Vulnerability · CVE-2026-30910
Crypt::Sodium::XS versions through 0.001000 for Perl has potential integer overflows.
Published Mar 8, 2026 · catalog updated Jun 17, 2026 · Crypt::Sodium::XS versions through 0.001000
Check if you run it
No confirmed exploitation is on record for CVE-2026-30910. EPSS is 0.35%. Act only if a listed version of Crypt::Sodium::XS versions through 0.001000 is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (Crypt::Sodium::XS versions through 0.001000).
- No version range is stored. A customer cannot check an installed version against this record.
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- High7.5
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.35%
- Remediation
- Advisory link
- Affected products
- cpe iamb/crypt
Crypt::Sodium::XS versions through 0.001000 for Perl has potential integer overflows. Combined aead encryption, combined signature creation, and bin2hex functions do not check that output size will be less than SIZE_MAX, which could lead to integer wraparound causing an undersized output buffer. This can cause a crash in bin2hex and encryption algorithms other than aes256gcm. For aes256gcm encryption and signatures, an undersized buffer could lead to buffer overflow. Encountering this issue is unlikely as the message length would need to be very large. For bin2hex the input size would have to be > SIZE_MAX / 2 For aegis encryption the input size would need to be > SIZE_MAX - 32U For other encryption the input size would need to be > SIZE_MAX - 16U For signatures the input size would need to be > SIZE_MAX - 64U
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe iamb/crypt\
How to fix CVE-2026-30910
Recommended remediation
A patch or advisory reference is linked. Open the original publisher for availability by product version.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-30910. EPSS is 0.35%. Act only if a listed version of Crypt::Sodium::XS versions through 0.001000 is installed.
Which versions are affected?
Compare what you have installed with \. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-190: Integer Overflow. EPSS 0.35%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Mar 8, 2026 · NIST NVD
Detected
Crypt::Sodium::XS versions through 0.001000 for Perl has potential integer overflows. Combined aead encryption, combined signature creation, and bin2hex functions do not check that output size will be less than SIZE_MAX, which could lead to integer wraparound causing an undersized output buffer. This can cause a crash in bin2hex and encryption algorithms other than aes256gcm. For aes256gcm encrypt
Jun 17, 2026 · NIST NVD
Updated
Crypt::Sodium::XS versions through 0.001000 for Perl has potential integer overflows. Combined aead encryption, combined signature creation, and bin2hex functions do not check that output size will be less than SIZE_MAX, which could lead to integer wraparound causing an undersized output buffer. This can cause a crash in bin2hex and encryption algorithms other than aes256gcm. For aes256gcm encrypt
Sources
- CVE.orgVulnerability recordCVE-2026-30910
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-30910
30-day exploitation probability 0.4%
first.org - NIST NVDVulnerability recordCVE-2026-30910
Crypt::Sodium::XS versions through 0.001000 for Perl has potential integer overflows. Combined aead encryption, combined signature creation, and bin2hex functions do not check that output size will be less than SIZE_MAX, which could lead to integer wraparound causing an undersiz
nvd.nist.gov
References
Freshness
Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.