Complete end-of-life dates, support windows, and security status for all Perl versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 5.26 | 5.26.3 | May 30, 2017 | May 30, 2020 | 2170 days past EOL | EOL |
| 5.28 | 5.28.3 | Jun 22, 2018 | Jun 23, 2021 | 1781 days past EOL | EOL |
| 5.30 | 5.30.3 | May 22, 2019 | May 22, 2022 | 1448 days past EOL | EOL |
| 5.32 | 5.32.1 | Jun 20, 2020 | Jun 20, 2023 | 1054 days past EOL | EOL |
| 5.34 | 5.34.3 | May 20, 2021 | May 20, 2024 | 719 days past EOL | EOL |
| 5.36 | 5.36.3 | May 27, 2022 | May 27, 2025 | 347 days past EOL | EOL |
| 5.38 | 5.38.5 | Jul 2, 2023 | Jul 2, 2026 | 54 days remaining | Warning |
| 5.40 | 5.40.4 | Jun 9, 2024 | Jun 9, 2027 | 396 days remaining | Active |
| 5.42 | 5.42.2 | Jul 3, 2025 | Jul 3, 2028 | 786 days remaining | Active |
When a Perl 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 Perl 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 →