CVE-2026-2597: 
Linux Debian vulnerability analysis and mitigation

Overview

CVE-2026-2597 is a heap-based buffer overflow vulnerability in the Perl module Crypt::SysRandom::XS affecting all versions before 0.010. The flaw exists in the XS function random_bytes(), which fails to validate that the length parameter is non-negative, leading to an integer wraparound and potential heap memory corruption. It was published on February 27, 2026, with a CVSS v3.1 base score of 7.5 (High) (Feedly, MetaCPAN).

Technical details

The root cause is classified as CWE-122 (Heap-based Buffer Overflow) and CWE-1284 (Improper Validation of Specified Quantity in Input). When a negative value (e.g., -1) is passed as the length argument to random_bytes(), the expression length + 1u causes an unsigned integer wraparound (CAPEC-92: Forced Integer Overflow), resulting in a near-zero-byte heap allocation. The subsequent call to the underlying random source (e.g., getrandom) receives the original negative value, which is implicitly cast to a very large unsigned integer (typically SIZE_MAX), causing writes far beyond the allocated buffer and resulting in heap memory corruption. In typical usage, the length argument is hardcoded by the caller, limiting attacker-controlled exploitation to applications that pass untrusted input to this parameter (Feedly, MetaCPAN).

Impact

Successful exploitation results in heap memory corruption, which can cause an application crash (denial of service). The primary impact is on availability (CVSS availability impact: High), with no direct confidentiality or integrity impact identified. Applications that expose the length parameter of random_bytes() to untrusted user input are at greatest risk; in common deployments where the length is hardcoded, the practical impact is limited to denial of service via crash (Feedly).

Exploitability

There is no public evidence of active in-the-wild exploitation or weaponized exploit code as of the time of this report. The EPSS score is approximately 0.028% (0.000280), indicating a very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation is further constrained by the requirement that the attacker control the length parameter passed to random_bytes(), which is uncommon in typical deployments (Feedly).

Exploitation steps

  1. Identify a vulnerable target: Locate a Perl application that uses Crypt::SysRandom::XS version before 0.010 and exposes the length parameter of random_bytes() to user-controlled input (e.g., via a web form, API, or configuration value).
  2. Supply a negative length value: Send a request or input that causes a negative integer (e.g., -1) to be passed as the length argument to random_bytes().
  3. Trigger integer wraparound: The expression length + 1u in the XS code wraps around due to unsigned arithmetic, resulting in a near-zero-byte heap allocation.
  4. Cause out-of-bounds write: The underlying system call (e.g., getrandom) receives the original negative value cast to a large unsigned integer, writing random bytes far beyond the allocated buffer.
  5. Achieve denial of service: The heap corruption causes the Perl application to crash, resulting in a denial of service condition (Feedly).

Indicators of compromise

  • Logs: Application crash logs or core dumps from Perl processes using Crypt::SysRandom::XS; error messages referencing random_bytes() or heap corruption.
  • Process: Unexpected termination of Perl application processes; segmentation faults or abort signals in system logs (e.g., /var/log/syslog, /var/log/messages).
  • File System: Presence of core dump files in the working directory of the affected Perl application.

Mitigation and workarounds

The vendor (LEONT) released version 0.010 of Crypt::SysRandom::XS, which addresses this vulnerability by adding validation to ensure the length parameter is non-negative. Users should upgrade to version 0.010 or later via CPAN (cpan Crypt::SysRandom::XS or cpanm Crypt::SysRandom::XS). Fedora has also issued updated packages for affected distributions. As a workaround where upgrading is not immediately possible, applications should validate that any user-supplied value passed to random_bytes() is a non-negative integer before invoking the function (MetaCPAN, Linux Security).

Community reactions

The vulnerability received coverage from Linux security news outlets including pro-linux.de and linuxsecurity.com, primarily in the context of Fedora package updates. The CPANSA database (Perl security advisory database) also catalogued the issue. No notable researcher commentary or significant social media discussion has been identified beyond routine vulnerability tracking (pro-linux.de, Linux Security, MetaCPAN CPANSA).

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Debian

Fixed

sid

libcrypt-sysrandom-xs-perl: 0.011-1

Fixed

Ubuntu

Unknown

devel

libcrypt-sysrandom-xs-perl

Not Affected

resolute

libcrypt-sysrandom-xs-perl

Unknown

resolute (esm-apps)

libcrypt-sysrandom-xs-perl

Unknown

Source: This report was generated using AI

Related Linux Debian vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-116612HIGH7.8
  • Linux Debian logoLinux Debian
  • gstreamer-editing-services1.0
NoYesOct 26, 2026
CVE-2026-115909HIGH7.5
  • Linux Debian logoLinux Debian
  • rust-zip
NoNoOct 26, 2026
CVE-2026-115907HIGH7.5
  • Linux Debian logoLinux Debian
  • rust-zip
NoNoOct 26, 2026
CVE-2026-115910MEDIUM6.8
  • Python logoPython
  • social-auth-core
NoYesOct 26, 2026
CVE-2026-2270MEDIUM5.9
  • NixOS logoNixOS
  • kubernetes
NoYesOct 26, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management