Unrated severityNVD Advisory· Published Mar 8, 2026· Updated Mar 10, 2026
Crypt::NaCl::Sodium versions through 2.002 for Perl has potential integer overflows
CVE-2026-30909
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
2- Range: <=2.002
- TIMLEGGE/Crypt::NaCl::Sodiumv5Range: 0
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
6- github.com/cpan-authors/crypt-nacl-sodium/pull/24.patchmitrepatch
- metacpan.org/release/TIMLEGGE/Crypt-NaCl-Sodium-2.003/source/Changesmitrerelease-notes
- metacpan.org/release/TIMLEGGE/Crypt-NaCl-Sodium-2.002/source/Sodium.xsmitre
- metacpan.org/release/TIMLEGGE/Crypt-NaCl-Sodium-2.002/source/Sodium.xsmitre
- metacpan.org/release/TIMLEGGE/Crypt-NaCl-Sodium-2.002/source/Sodium.xsmitre
- metacpan.org/release/TIMLEGGE/Crypt-NaCl-Sodium-2.002/source/Sodium.xsmitre
News mentions
0No linked articles in our index yet.