What’s Vulnerable › Vulnerabilities

CVE-2026-30909: Crypt::NaCl::Sodium versions through 2.002 for Perl has potential integer overflows

• Severity: critical (CVSS 9.8 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.6% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-03-08 · updated 2026-06-17
• Weakness: CWE-190

Description

Crypt::NaCl::Sodium versions through 2.002 for Perl has potential integer overflows. bin2hex, encrypt, aes256gcm_encrypt_afternm and seal functions do not check that output size will be less than SIZE_MAX, which could lead to integer wraparound causing an undersized output buffer. Encountering this issue is unlikely as the message length would need to be very large. For bin2hex() the bin_len would have to be > SIZE_MAX / 2 For encrypt() the msg_len would need to be > SIZE_MAX - 16U For aes256gcm_encrypt_afternm() the msg_len would need to be > SIZE_MAX - 16U For seal() the enc_len would need to be > SIZE_MAX - 64U

Affected products

• TIMLEGGE Crypt::Nacl::Sodium: before 2.003 — fixed in 2.003

How to fix

Upgrade to a fixed version: TIMLEGGE Crypt::Nacl::Sodium 2.003. Check the vendor advisory for mitigations.

References

• https://github.com/cpan-authors/crypt-nacl-sodium/pull/24.patch
• https://metacpan.org/release/TIMLEGGE/Crypt-NaCl-Sodium-2.002/source/Sodium.xs#L2116
• https://metacpan.org/release/TIMLEGGE/Crypt-NaCl-Sodium-2.002/source/Sodium.xs#L2310
• https://metacpan.org/release/TIMLEGGE/Crypt-NaCl-Sodium-2.002/source/Sodium.xs#L3304
• https://metacpan.org/release/TIMLEGGE/Crypt-NaCl-Sodium-2.002/source/Sodium.xs#L942
• https://metacpan.org/release/TIMLEGGE/Crypt-NaCl-Sodium-2.003/source/Changes
• http://www.openwall.com/lists/oss-security/2026/03/08/1

Get alerted when CVE-2026-30909 or the next vulnerability affects your stack