Security Advisories (3)
CVE-2026-57432 (2026-07-13)

Perl versions through 5.43.10 have an integer overflow in S_measure_struct leading to an out-of-bounds heap read in pack and unpack. S_measure_struct adds each item's size times its repeat count to a running total with no overflow check, so a large repeat count in a pack or unpack template wraps the signed SSize_t total negative. The @, X, and x position codes then guard their moves with a signed length comparison that passes when the length is negative, advancing the buffer pointer out of bounds. A template derived from untrusted input can read heap memory past the buffer and return it to the caller.

CVE-2026-13221 (2026-07-13)

Perl versions through 5.43.9 produce silently incorrect regular expression matches when an alternation of more than 65535 fixed string branches is compiled into a trie in Perl_study_chunk. When such branches are combined into a trie, the delta between the first branch and the shared tail is stored in a 16-bit field. A branch count above 65535 overflows the field, and the trie's match decision table is truncated with no warning or error. A pattern of this shape produces false positive matches (matching strings it should not) and false negative matches (failing to match strings it should). When such a pattern gates an access or filtering decision, the result is wrong.

CVE-2026-8376 (2026-05-25)

Perl versions through 5.43.10 have a heap buffer overflow when compiling regular expressions with a repeated fixed string on 32-bit builds. Perl_study_chunk in regcomp_study.c checked the size of the joined substring buffer in characters rather than bytes. For a quantified fixed substring with a large minimum count, the byte length mincount * l could overflow SSize_t, producing an undersized SvGROW allocation; the subsequent copy writes past the end of the buffer. A caller that compiles an attacker-controlled regular expression on a 32-bit perl build triggers a heap buffer overflow at compile time.

NAME

valgrindpp.pl - A post processor for make test.valgrind

SYNOPSIS

valgrindpp.pl [--dir=dir] [--frames=number] [--hide=identifier] [--lines] [--output-file=file] [--tests] [--top=number] [--verbose]

DESCRIPTION

valgrindpp.pl is a post processor for .valgrind files created during make test.valgrind. It collects all these files, extracts most of the information and produces a significantly shorter summary of all detected memory access errors and memory leaks.

OPTIONS

--dir=dir

Recursively process .valgrind files in dir. If this options is not given, valgrindpp.pl must be run from either the perl source or the t directory and will process all .valgrind files within the distribution.

--frames=number

Number of stack frames within the perl source code to consider when distinguishing between memory leak sources. Increasing this value will give you a longer backtrace, while decreasing the number will show you fewer sources for memory leaks. The default is 3 frames.

--hide=identifier

Hide all memory leaks that have identifier in their backtrace. Useful if you want to hide leaks from functions that are known to have lots of memory leaks. identifier can also be a regular expression, in which case all leaks with symbols matching the expression are hidden. Can be given multiple times.

--lines

Show line numbers for stack frames. This is useful for further increasing the error/leak resolution, but makes it harder to compare different reports using diff.

--output-file=file

Redirect the output into file. If this option is not given, the output goes to stdout.

--tests

List all tests that trigger memory access errors or memory leaks explicitly instead of only printing a count.

--top=number

List the top number test scripts for memory access errors and memory leaks. Set to 0 for no top-n statistics.

--verbose

Increase verbosity level. Can be given multiple times.

COPYRIGHT

Copyright 2003 by Marcus Holland-Moritz <mhx@cpan.org>.

This program is free software; you may redistribute it and/or modify it under the same terms as Perl itself.