CVE-2026-2474

libcrypt-urandom-perl: Crypt::URandom versions from 0.41 before 0.55 for Perl is vulnerable to a heap buffer overflow in the XS function cry...

CVE-2026-2474 is fixed in 5 products on 1 platform, first by DEBIAN-CVE-2026-2474, released February 16, 2026. It is not reported as exploited. Patch Radar priority: High.

High
CVSS
7.5
high
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0035
28th percentile

Crypt::URandom versions from 0.41 before 0.55 for Perl is vulnerable to a heap buffer overflow in the XS function crypt_urandom_getrandom(). The function does not validate that the length parameter is non-negative. If a negative value (e.g. -1) is supplied, the expression length + 1u causes an integer wraparound, resulting in a zero-byte allocation. The subsequent call to getrandom(data, length, GRND_NONBLOCK) passes the original negative value, which is implicitly converted to a large unsigned value (typically SIZE_MAX). This can result in writes beyond the allocated buffer, leading to heap memory corruption and application crash (denial of service). In common usage, the length argument is typically hardcoded by the caller, which reduces the likelihood of attacker-controlled exploitation. Applications that pass untrusted input to this parameter may be affected.

Where it's fixed

ProductFixed inFixReleased
Linux
libcrypt-urandom-perl · Debian 13.5 (trixie) 0.54-1+deb13u1 DEBIAN-CVE-2026-2474 Feb 16, 2026
libcrypt-urandom-perl · Debian 14 0.55-1 DEBIAN-CVE-2026-2474 Feb 16, 2026
perl-Crypt-URandom · Fedora 43 0.55-1.fc43 FEDORA-2026-88F1155B8B Feb 23, 2026
perl-Crypt-URandom-debuginfo · Fedora 43 0.55-1.fc43 FEDORA-2026-88F1155B8B Feb 23, 2026
perl-Crypt-URandom-debugsource · Fedora 43 0.55-1.fc43 FEDORA-2026-88F1155B8B Feb 23, 2026
perl-Crypt-URandom-tests · Fedora 43 0.55-1.fc43 FEDORA-2026-88F1155B8B Feb 23, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.