/ 
perl-5.27.7
⭐ Starred 2013
/ release_schedule
Security Advisories (8)
CVE-2020-12723 (2020-06-05)

regcomp.c in Perl before 5.30.3 allows a buffer overflow via a crafted regular expression because of recursive S_study_chunk calls.

CVE-2020-10878 (2020-06-05)

Perl before 5.30.3 has an integer overflow related to mishandling of a "PL_regkind[OP(n)] == NOTHING" situation. A crafted regular expression could lead to malformed bytecode with a possibility of instruction injection.

CVE-2020-10543 (2020-06-05)

Perl before 5.30.3 on 32-bit platforms allows a heap-based buffer overflow because nested regular expression quantifiers have an integer overflow.

CVE-2018-6798 (2018-04-17)

An issue was discovered in Perl 5.22 through 5.26. Matching a crafted locale dependent regular expression can cause a heap-based buffer over-read and potentially information disclosure.

CVE-2023-47100

In Perl before 5.38.2, S_parse_uniprop_string in regcomp.c can write to unallocated space because a property name associated with a \p{...} regular expression construct is mishandled. The earliest affected version is 5.30.0.

CVE-2024-56406 (2025-04-13)

A heap buffer overflow vulnerability was discovered in Perl. When there are non-ASCII bytes in the left-hand-side of the `tr` operator, `S_do_trans_invmap` can overflow the destination pointer `d`.    $ perl -e '$_ = "\x{FF}" x 1000000; tr/\xFF/\x{100}/;'    Segmentation fault (core dumped) It is believed that this vulnerability can enable Denial of Service and possibly Code Execution attacks on platforms that lack sufficient defenses.

CVE-2025-40909 (2025-05-30)

Perl threads have a working directory race condition where file operations may target unintended paths. If a directory handle is open at thread creation, the process-wide current working directory is temporarily changed in order to clone that handle for the new thread, which is visible from any third (or more) thread already running. This may lead to unintended operations such as loading code or accessing files from unexpected locations, which a local attacker may be able to exploit. The bug was introduced in commit 11a11ecf4bea72b17d250cfb43c897be1341861e and released in Perl version 5.13.6

CVE-2023-47039 (2023-10-30)

Perl for Windows relies on the system path environment variable to find the shell (cmd.exe). When running an executable which uses Windows Perl interpreter, Perl attempts to find and execute cmd.exe within the operating system. However, due to path search order issues, Perl initially looks for cmd.exe in the current working directory. An attacker with limited privileges can exploit this behavior by placing cmd.exe in locations with weak permissions, such as C:\ProgramData. By doing so, when an administrator attempts to use this executable from these compromised locations, arbitrary code can be executed.

NAME

release_schedule - Perl 5 release schedule

STABLE RELEASE SCHEDULE

This schedule lists the projected or historical development and release schedules for the next, current and previous stable versions of Perl. Dates with two or more question marks will only be releases if deemed necessary by the Pumpking.

Perl 5.28

Code freezes (which happen in the 5.27.X series)

2018-01-20  5.27.8          Contentious changes freeze
2018-02-20  5.27.9          User-visible changes to correctly
                            functioning programs freeze
2018-03-20  5.27.10         Full code freeze
2018-04-20  5.28.0          Stable release!

Perl 5.26

2017-05-30  5.26.0 ✓        Sawyer X
2017-09-22  5.26.1 ✓        Steve Hay

Perl 5.24

2016-05-09  5.24.0 ✓        Ricardo Signes
2017-01-14  5.24.1 ✓        Steve Hay
2017-07-15  5.24.2 ✓        Steve Hay
2017-09-22  5.24.3 ✓        Steve Hay

Perl 5.22

2015-06-01  5.22.0 ✓        Ricardo Signes
2015-12-13  5.22.1 ✓        Steve Hay
2016-04-29  5.22.2 ✓        Steve Hay
2017-01-14  5.22.3 ✓        Steve Hay
2017-07-15  5.22.4 ✓        Steve Hay

DEVELOPMENT RELEASE SCHEDULE

This schedule lists the release engineers for at least the next four months of releases of bleadperl. If there are fewer than four months listed as you make a release, it's important that you extend the schedule AND identify the next release engineer.

Before adding a release engineer, you must contact them and they must consent to ship the release.

When shipping a release, you should include the schedule for (at least) the next four releases. If a stable version of Perl is released, you should reset the version numbers to the next blead series.

Perl 5.27

2017-05-31  5.27.0 ✓        Sawyer X
2017-06-20  5.27.1 ✓        Eric Herman
2017-07-20  5.27.2 ✓        Aaron Crane
2017-08-20  5.27.3 ✓        Matthew Horsfall
2017-09-20  5.27.4 ✓        John Anderson
2017-10-20  5.27.5 ✓        Steve Hay
2017-11-20  5.27.6 ✓        Karen Etheridge
2017-12-20  5.27.7          BinGOs
2018-01-20  5.27.8          Abigail
2018-02-20  5.27.9          Renee Backer
2018-03-20  5.27.10         Todd Rinaldo

(RC0 for 5.28.0 will be released once we think that all the blockers have been addressed. This typically means some time in April or May.)

VICTIMS

The following porters have all consented to do at least one release of bleadperl. If you can't do a release and can't find a substitute amongst this list, mail p5p.

(Please do not add any names to this list without prior consent of the Pumpking.)

Abigail <abigail@abigail.be>
Aristotle Pagaltzis <pagaltzis@gmx.de>
Ask Bjørn Hansen <ask@perl.org>
Chris Williams <bingos@cpan.org>
Dave Cross <dave@perlhacks.com>
Dave Rolsky <autarch@urth.org>
David Golden <dagolden@cpan.org>
Florian Ragwitz <rafl@debian.org>
Jesse Luehrs <doy@cpan.org>
Jesse Vincent <jesse@cpan.org>
Leon Brocard <acme@astray.com>
Matt Trout <mst@shadowcat.co.uk>
Matthew Horsfall <wolfsage@gmail.com>
Max Maischein <corion@cpan.org>
Peter Martini <petercmartini@gmail.com>
Philippe Bruhat <book@cpan.org>
Ricardo Signes <rjbs@cpan.org>
Stevan Little <stevan@cpan.org>
Steve Hay <steve.m.hay@googlemail.com>
Tatsuhiko Miyagawa <miyagawa@bulknews.net>
Tony Cook <tony@develop-help.com>
Yves Orton <demerphq@gmail.com>
Zefram <zefram@fysh.org>
Ævar Arnfjörð Bjarmason <avar@cpan.org>

AUTHOR

Jesse Vincent <jesse@cpan.org>