/ 
perl-5.43.9
⭐ Starred 2013 / less
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

less - perl pragma to request less of something

SYNOPSIS

use less 'CPU';

DESCRIPTION

This is a user-pragma. If you're very lucky some code you're using will know that you asked for less CPU usage or ram or fat or... we just can't know. Consult your documentation on everything you're currently using.

For general suggestions, try requesting CPU or memory.

use less 'memory';
use less 'CPU';
use less 'fat';

If you ask for nothing in particular, you'll be asking for less 'please'.

use less 'please';

FOR MODULE AUTHORS

less has been in the core as a "joke" module for ages now and it hasn't had any real way to communicating any information to anything. Thanks to Nicholas Clark we have user pragmas (see perlpragma) and now less can do something.

You can probably expect your users to be able to guess that they can request less CPU or memory or just "less" overall.

If the user didn't specify anything, it's interpreted as having used the please tag. It's up to you to make this useful.

# equivalent
use less;
use less 'please';

BOOLEAN = less->of( FEATURE )

The class method less->of( NAME ) returns a boolean to tell you whether your user requested less of something.

if ( less->of( 'CPU' ) ) {
    ...
}
elsif ( less->of( 'memory' ) ) {

}

FEATURES = less->of()

If you don't ask for any feature, you get the list of features that the user requested you to be nice to. This has the nice side effect that if you don't respect anything in particular then you can just ask for it and use it like a boolean.

if ( less->of ) {
    ...
}
else {
    ...
}

CAVEATS

This probably does nothing.
This works only on 5.10+

At least it's backwards compatible in not doing much.