CVE-2026-2597 Affecting libcrypt-sysrandom-xs-perl package, versions <0.011-1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIANUNSTABLE-LIBCRYPTSYSRANDOMXSPERL-15325671
- published22 Feb 2026
- disclosed27 Feb 2026
Introduced: 22 Feb 2026
CVE-2026-2597 (opens in a new tab)How to fix?
Upgrade Debian:unstable libcrypt-sysrandom-xs-perl to version 0.011-1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream libcrypt-sysrandom-xs-perl package and not the libcrypt-sysrandom-xs-perl package as distributed by Debian.
See How to fix? for Debian:unstable relevant fixed versions and status.
Crypt::SysRandom::XS versions before 0.010 for Perl is vulnerable to a heap buffer overflow in the XS function random_bytes().
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 chosen random function (e.g. getrandom) 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.