Security Advisories (3)
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-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-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

ptargrep - Apply pattern matching to the contents of files in a tar archive

SYNOPSIS

ptargrep [options] <pattern> <tar file> ...

Options:

 --basename|-b     ignore directory paths from archive
 --ignore-case|-i  do case-insensitive pattern matching
 --list-only|-l    list matching filenames rather than extracting matches
 --verbose|-v      write debugging message to STDERR
 --help|-?         detailed help message

DESCRIPTION

This utility allows you to apply pattern matching to the contents of files contained in a tar archive. You might use this to identify all files in an archive which contain lines matching the specified pattern and either print out the pathnames or extract the files.

The pattern will be used as a Perl regular expression (as opposed to a simple grep regex).

Multiple tar archive filenames can be specified - they will each be processed in turn.

OPTIONS

--basename (alias -b)

When matching files are extracted, ignore the directory path from the archive and write to the current directory using the basename of the file from the archive. Beware: if two matching files in the archive have the same basename, the second file extracted will overwrite the first.

--ignore-case (alias -i)

Make pattern matching case-insensitive.

--list-only (alias -l)

Print the pathname of each matching file from the archive to STDOUT. Without this option, the default behaviour is to extract each matching file.

--verbose (alias -v)

Log debugging info to STDERR.

--help (alias -?)

Display this documentation.

COPYRIGHT

Copyright 2010 Grant McLean <grantm@cpan.org>

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