Service crash or memory corruption via size wraparound
Published Mar 8, 2026 · Updated Mar 8, 2026
Integer overflow in Crypt::Sodium::XS 0.001000 and earlier allows remote attackers to crash a service via an oversized message. The combined AEAD, signature, and bin2hex paths add expansion bytes to message lengths without first proving the result is below SIZE_MAX, so allocation sizes wrap. Triggering requires messages near SIZE_MAX; bin2hex and most encryption paths crash, while aes256gcm and signature paths can overwrite an undersized buffer.
Summary
What happened
Integer overflow in Crypt::Sodium::XS 0.001000 and earlier allows remote attackers to crash a service via an oversized message. The combined AEAD, signature, and bin2hex paths add expansion bytes to message lengths without first proving the result is below SIZE_MAX, so allocation sizes wrap. Triggering requires messages near SIZE_MAX; bin2hex and most encryption paths crash, while aes256gcm and signature paths can overwrite an undersized buffer.
The record
- CVE
- CVE-2026-30910
- Published
- Mar 8, 2026
- Updated
- Mar 8, 2026
- Vendor
- Brad Barden
- Product
- Crypt::Sodium::XS
- Classifications
- CWE-190, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 8, 2026CVE publishedPublication date reported by the CVE source.
- Mar 8, 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 <=0.001000
What conditions does exploitation require?
What is affected?
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