PERL5362DELTA(1perl)

๐Ÿ“ฆ
version 5.44.0 ยท 2 versions
, in arch rolling

๐Ÿ’– PERL5362DELTA ๐Ÿ’–

okay bestie, welcome to perl5362delta โ€” this is the Perl Programmers Reference Guide entry that spills all the tea on what is new for perl v5.36.2. ๐ŸŽ€


โœจ DESCRIPTION โœจ

So this doc literally describes the differences between the 5.36.1 release and the 5.36.2 release. That's it, that's the whole vibe. ๐Ÿ’…

But lowkey, if you're upgrading from an earlier release โ€” like say 5.36.0 โ€” you gotta do your homework first, bestie. Read perl5361delta first, because that one describes the differences between 5.36.0 and 5.36.1. Skipping steps is not the move here, fr fr. ๐Ÿ“š


๐Ÿ”’ Security ๐Ÿ”’

This release fixes the following security issues. Not me being dramatic butโ€ฆ these are the important ones, no cap. ๐Ÿšจ

๐Ÿฉธ CVE-2023-47038 - Write past buffer end via illegal user-defined Unicode property

This vulnerability was reported directly to the Perl security team by Nathan Mills the.true.nathan.mills@gmail.com. Shoutout to them for doing the right thing, iconic behavior honestly. ๐Ÿซถ

So here's the situation: a crafted regular expression, when compiled by perl 5.30.0 through 5.38.0, can cause a one-byte attacker controlled buffer overflow in a heap allocated buffer. That's it. That's the whole problem. Do not pass go, do not collect $200. ๐Ÿ’€

๐ŸชŸ CVE-2023-47039 - Perl for Windows binary hijacking vulnerability

This vulnerability was reported to the Intel Product Security Incident Response Team (PSIRT) by GitHub user ycdxsb <https://github.com/ycdxsb/WindowsPrivilegeEscalation>. PSIRT then reported it to the Perl security team. chain of custody? slay. โœจ

Here's the lore: 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 โ€” and this is the messy part โ€” 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. So yeah. Be careful out there. ๐Ÿ˜ญ


๐ŸŒธ Acknowledgements ๐ŸŒธ

Perl 5.36.2 represents approximately 1 month of development since Perl 5.36.1 and contains approximately 2,300 lines of changes across 38 files from 4 authors. Their commitment to the bit? unmatched. ๐Ÿ‘‘

Excluding auto-generated files, documentation and release tools, there were approximately 1,400 lines of changes to 8 .pm, .t, .c and .h files. numbers! we love numbers! ๐Ÿงฎ

Perl continues to flourish into its fourth decade thanks to a vibrant community of users and developers. The following people are known to have contributed the improvements that became Perl 5.36.2:

  • Karl Williamson
  • Paul Evans
  • Steve Hay
  • Tony Cook

The list above is almost certainly incomplete as it is automatically generated from version control history. In particular, it does not include the names of the (very much appreciated) contributors who reported issues to the Perl bug tracker. so if you're not on the list, you're still loved, bestie ๐Ÿ’–

Many of the changes included in this version originated in the CPAN modules included in Perl's core. We're grateful to the entire CPAN community for helping Perl to flourish. CPAN girlies rise up ๐Ÿฆ‹

For a more complete list of all of Perl's historical contributors, please see the AUTHORS file in the Perl source distribution.


๐Ÿ› Reporting Bugs ๐Ÿ›

If you find what you think is a bug, you might check the perl bug database at <https://github.com/Perl/perl5/issues>. There may also be information at <http://www.perl.org/>, the Perl Home Page. always do your research before you @ anyone, iykyk ๐Ÿ‘€

If you believe you have an unreported bug, please open an issue at <https://github.com/Perl/perl5/issues>. Be sure to trim your bug down to a tiny but sufficient test case. it's giving minimal reproducible example and honestly? respecting it ๐ŸŒˆ

If the bug you are reporting has security implications which make it inappropriate to send to a public issue tracker, then see "SECURITY VULNERABILITY CONTACT INFORMATION" in perlsec for details of how to report the issue. do NOT just post it publicly, we beg ๐Ÿ™ˆ

๐Ÿ™ Give Thanks ๐Ÿ™

If you wish to thank the Perl 5 Porters for the work we had done in Perl 5, you can do so by running the perlthanks program:

perlthanks

This will send an email to the Perl 5 Porters list with your show of thanks. a little gratitude goes a long way, and honestly? they deserve it ๐Ÿ’Œ


๐Ÿ‘€ SEE ALSO ๐Ÿ‘€

  • The Changes file for an explanation of how to view exhaustive details on what changed. exhaustive is the keyword here, it's giving encyclopedia ๐Ÿ“–
  • The INSTALL file for how to build Perl. builder besties assemble ๐Ÿ”จ
  • The README file for general stuff. the vibes document, essentially โœจ
  • The Artistic and Copying files for copyright information. legal girlies get a moment too โš–๏ธ

okay that's the whole page, you're officially caught up on perl5362delta ๐ŸŒŸ this little doc came to you from perl v5.44.0, dated 2026-10-17, and it's part of the PERL5362DELTA(1perl) fam. go forth and update responsibly, bestie ๐Ÿ’…๐Ÿ’–

๐Ÿ“ฆ where this page comes from
  • arch rolling: perl 5.44.0-1 ยท Artistic-1.0-Perl AND GPL-1.0-or-later
  • ๐Ÿ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms