Integer overflow in Timlegge Crypt::nacl::sodium
CVE-2026-30909
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
Vulnerability class: Integer Overflow
Published · last modified .
CVSS v3 metric
CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS 0.006, 48.7th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
Weakness classification (CWE)
References
- metacpan.org/release/TIMLEGGE/Crypt-NaCl-Sodium-2.002/source/Sodium.xs (Product)
- metacpan.org/release/TIMLEGGE/Crypt-NaCl-Sodium-2.002/source/Sodium.xs (Product)
- metacpan.org/release/TIMLEGGE/Crypt-NaCl-Sodium-2.002/source/Sodium.xs (Product)
- metacpan.org/release/TIMLEGGE/Crypt-NaCl-Sodium-2.002/source/Sodium.xs (Product)
- github.com/cpan-authors/crypt-nacl-sodium/pull/24.patch (Patch, patch)
- metacpan.org/release/TIMLEGGE/Crypt-NaCl-Sodium-2.003/source/Changes (release-notes, Release Notes)
- www.openwall.com/lists/oss-security/2026/03/08/1 (Mailing List, Third Party Advisory)