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

git-deltatool - Annotate commits for perldelta

SYNOPSIS

# annotate commits back to last 'git describe' tag

$ git-deltatool

# review annotations

$ git-deltatool --mode review

# review commits needing help

$ git-deltatool --mode review --type blocking

# summarize commits needing help

$ git-deltatool --mode summary --type blocking

# assemble annotations by section to STDOUT

$ git-deltatool --mode render

# Get a list of commits needing further review, e.g. for peer review

$ git-deltatool --mode summary --type blocking

# mark 'pending' annotations as 'done' (i.e. added to perldelta)

$ git-deltatool --mode update --type pending --status done

OPTIONS

--mode|-m MODE

Indicates the run mode for the program. The default is 'assign' which assigns categories and marks the notes as 'pending' (or 'ignored'). Other modes are 'review', 'render', 'summary' and 'update'.

--type|-t TYPE

Indicates what types of commits to process. The default for 'assign' mode is 'new', which processes commits without any perldelta notes. The default for 'review', 'summary' and 'render' modes is 'pending'. The options must be set explicitly for 'update' mode.

The type 'blocking' is reserved for commits needing further review.

--status|-s STATUS

For 'update' mode only, sets a new status. While there is no restriction, it should be one of 'new', 'pending', 'blocking', 'ignored' or 'done'.

--since REVISION

Defines the boundary for searching git commits. Defaults to the last major tag (as would be given by 'git describe').

--help

Shows the manual.

TODO

It would be nice to make some of the structured sections smarter -- e.g. look at changed files in pod/* for Documentation section entries. Likewise it would be nice to collate them during the render phase -- e.g. cluster all platform-specific things properly.

AUTHOR

David Golden <dagolden@cpan.org>

COPYRIGHT AND LICENSE

This software is copyright (c) 2010 by David Golden.

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