Complete end-of-life dates, support windows, and security status for all Sns Firmware versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1 | — | Jun 3, 2014 | Apr 24, 2015 | 4033 days past EOL | EOL |
| 2 | — | Mar 31, 2015 | Sep 13, 2021 | 1699 days past EOL | EOL |
| 3 | — | Nov 21, 2016 | Sep 24, 2020 | 2053 days past EOL | EOL |
| 3.7 LTS | — | Sep 29, 2018 | Jun 30, 2024 | 678 days past EOL | EOL |
| 4.0 | — | Jan 7, 2020 | Sep 24, 2020 | 2053 days past EOL | EOL |
| 3.11 LTS | — | Sep 24, 2020 | Jun 30, 2024 | 678 days past EOL | EOL |
| 4.1 | — | Sep 24, 2020 | Apr 6, 2021 | 1859 days past EOL | EOL |
| 4.2 | — | Apr 6, 2021 | Jul 21, 2022 | 1388 days past EOL | EOL |
| 4.3 LTS | — | Jan 12, 2022 | Mar 31, 2026 | 39 days past EOL | EOL |
| 4.4 | — | May 12, 2022 | Jun 30, 2022 | 1409 days past EOL | EOL |
| 4.5 | — | Jul 5, 2022 | Nov 24, 2022 | 1262 days past EOL | EOL |
| 4.6 | — | Nov 24, 2022 | May 22, 2024 | 717 days past EOL | EOL |
| 4.7 | — | Oct 31, 2023 | Feb 12, 2025 | 451 days past EOL | EOL |
| 4.8 LTS | — | Jul 2, 2024 | Already EOL | Supported | Active |
| 5.0 | — | Sep 24, 2025 | Already EOL | Supported | Active |
When a Sns Firmware version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Sns Firmware should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →