Memory corruption via undersized length pointer
Published Feb 22, 2026 · Updated Feb 22, 2026
Integer overflow in Crypt::NaCl::Sodium 2.001 and earlier allows remote attackers to corrupt memory through cryptographic operations. Sodium.xs passes a 32-bit STRLEN address to libsodium as an unsigned long long pointer, so an eight-byte returned length overwrites adjacent memory. The flaw is reachable only on 32-bit systems when consuming software invokes affected encryption, decryption, or signing paths with attacker-influenced data, causing memory corruption or a crash.
Summary
What happened
Integer overflow in Crypt::NaCl::Sodium 2.001 and earlier allows remote attackers to corrupt memory through cryptographic operations. Sodium.xs passes a 32-bit STRLEN address to libsodium as an unsigned long long pointer, so an eight-byte returned length overwrites adjacent memory. The flaw is reachable only on 32-bit systems when consuming software invokes affected encryption, decryption, or signing paths with attacker-influenced data, causing memory corruption or a crash.
The record
- CVE
- CVE-2026-2588
- Published
- Feb 22, 2026
- Updated
- Feb 22, 2026
- Vendor
- Timothy Legge
- Product
- Crypt::NaCl::Sodium
- Classifications
- CWE-190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 22, 2026CVE publishedPublication date reported by the CVE source.
- Feb 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.001
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo