CVE-2026-30910
Integer Overflow in Crypt::Sodium::XS Causes Buffer Overflow Risk
Publication date: 2026-03-08
Last updated on: 2026-03-10
Assigner: CPANSec
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| iamb | crypt | to 0.001001 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-190 | The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Crypt::Sodium::XS versions through 0.001000 for Perl and involves potential integer overflows.
Specifically, the combined AEAD encryption, combined signature creation, and bin2hex functions do not verify that the output size will be less than SIZE_MAX. This lack of checking can cause an integer wraparound, resulting in an undersized output buffer.
The undersized buffer can cause a crash in bin2hex and encryption algorithms other than aes256gcm. For aes256gcm encryption and signatures, it could lead to a buffer overflow.
However, triggering this issue is unlikely because it requires very large message lengths, such as input sizes greater than SIZE_MAX divided by 2 for bin2hex, or close to SIZE_MAX minus a small constant for encryption and signature functions.
How can this vulnerability impact me? :
This vulnerability can impact you by causing crashes or buffer overflows when processing very large inputs with Crypt::Sodium::XS.
A crash could lead to denial of service, disrupting the availability of applications using these functions.
In the case of aes256gcm encryption and signatures, a buffer overflow could potentially lead to memory corruption, which might be exploited for arbitrary code execution or other security breaches.
However, the likelihood of encountering this vulnerability is low because it requires extremely large input sizes.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know