Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:HSummary
CVE-2026-2588 is a critical-severity Integer Overflow or Wraparound (CWE-190) vulnerability in Timlegge Crypt\. Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 27th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-2588 is an integer overflow vulnerability (CWE-190) affecting Crypt::NaCl::Sodium versions through 2.001 for Perl, specifically on 32-bit systems. The flaw occurs in the Sodium.xs module, where a STRLEN (size_t) value is cast to an unsigned long long when passing a length pointer to libsodium functions. On 32-bit platforms, size_t is typically 32 bits, while unsigned long long is at least 64 bits, enabling the overflow.
Remote attackers require no privileges or user interaction to exploit this over the network with low complexity, as indicated by the CVSS v3.1 base score of 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H). Successful exploitation can result in high integrity and availability impacts, potentially leading to crashes, denial of service, or manipulation of cryptographic operations due to incorrect length handling in libsodium calls.
Mitigation involves applying patches from the Crypt::NaCl::Sodium repository, such as commits 557388bdb4da416a56663cda0154b80cd524395c and 8cf7f66ba922443e131c9deae1ee00fafe4f62e4, which address the casting issue in Sodium.xs (e.g., around line 2119 in version 2.001 source). Security practitioners should upgrade to a patched version and verify deployments on 32-bit Perl environments using libsodium.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-7558
Vulnerability Data
Crypt::NaCl::Sodium versions through 2.001 for Perl has an integer overflow flaw on 32-bit systems. Sodium.xs casts a STRLEN (size_t) to unsigned long long when passing a length pointer to libsodium functions. On 32-bit systems size_t is typically 32-bits while an…
more
unsigned long long is at least 64-bits.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.2.6
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (static analysis, fuzzing, unit tests) directly finds integer overflow defects before deployment.
Secure engineering principles require use of safe arithmetic constructs or language features that structurally eliminate integer overflow during calculation.
Input validation enforces bounds on values before arithmetic, stopping the conditions that trigger overflow or wraparound.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require use of safe arithmetic, bounds checks, and testing that prevent integer overflows.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect integer overflows before release.
Secure SDLC mandates input validation and arithmetic checks that prevent integer overflows.
Application security requirements include bounds checking and safe arithmetic to avoid overflow conditions.
Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.
Secure coding standards explicitly forbid unsafe integer operations and mandate overflow-safe constructs.