Complete end-of-life dates, support windows, and security status for all Neos versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 7.3 LTS | 7.3.21 | Dec 8, 2021 | Mar 31, 2025 | 404 days past EOL | EOL |
| 8.0 | 8.0.19 | Apr 1, 2022 | Mar 31, 2025 | 404 days past EOL | EOL |
| 8.1 | 8.1.14 | Sep 2, 2022 | Mar 31, 2025 | 404 days past EOL | EOL |
| 8.2 | 8.2.14 | Dec 1, 2022 | Mar 31, 2025 | 404 days past EOL | EOL |
| 8.3 LTS | 8.3.33 | Apr 24, 2023 | Sep 1, 2027 | 480 days remaining | Active |
| 9.0 | 9.0.11 | Apr 3, 2025 | Apr 1, 2028 | 693 days remaining | Active |
| 8.4 LTS | 8.4.5 | Oct 10, 2025 | Sep 1, 2027 | 480 days remaining | Active |
| 9.1 | 9.1.4 | Dec 17, 2025 | Apr 1, 2028 | 693 days remaining | Active |
When a Neos 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 Neos 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 →