EOL.Wiki EOL.Wiki
← ← Back to all products

Perl

Active
Programming Languages Latest Version: 5.42.0 Latest Release: Jul 3, 2025

Perl is a highly capable, feature-rich programming language known for text processing and system administration.

Versions

9

Latest Version

5.42.0

Active Support

2

EOL

6

Lifecycle Timeline

Today
5.42
5.42
5.40
5.40
5.38
5.38
5.36
5.36
5.34
5.34
5.32
5.32
5.30
5.30
5.28
5.28
5.26
5.26
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
5.42Jul 3, 2025YesJul 3, 20285.42.0No
Active
5.40Jun 9, 2024YesJun 9, 20275.40.3No
Active
5.38Jul 2, 2023Jul 3, 2025Jul 2, 20265.38.5No
Security
5.36May 27, 2022Jun 9, 2024May 27, 20255.36.3No
EOL
5.34May 20, 2021Jul 2, 2023May 20, 20245.34.3No
EOL
5.32Jun 20, 2020May 27, 2022Jun 20, 20235.32.1No
EOL
5.30May 22, 2019May 20, 2021May 22, 20225.30.3No
EOL
5.28Jun 22, 2018Jun 20, 2020Jun 23, 20215.28.3No
EOL
5.26May 30, 2017May 22, 2019May 30, 20205.26.3No
EOL

Frequently Asked Questions

Which versions of Perl have reached end of life?
The following Perl versions have reached end of life and no longer receive security updates: 5.36, 5.34, 5.32, 5.30, 5.28, 5.26. It is recommended to upgrade to a supported version.
Is it safe to continue using Perl 5.36?
Perl 5.36 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Perl?
The latest version of Perl is 5.42.0, released in the 5.42 release cycle.
How many versions of Perl are currently supported?
Perl currently has 3 actively supported version(s): 5.42, 5.40, 5.38.
When does Perl 5.42 reach end of life?
Perl 5.42 is scheduled to reach end of life on Jul 3, 2028.
What should I do when Perl reaches end of life?
When a Perl version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.