by Kastro
Paper/Archive/CVE-2026-30909

CVE-2026-30909

TIMLEGGE Crypt::NaCl::Sodium — Crypt::NaCl::Sodium versions through 2.002 for Perl has potential integer overflows

EPSS 0.6%CVSS 9.8
critical.is priorityof 100
39
CVSS 9.8 (ADP, NVD agree)9.8 / 10 × 3029.4Not in CISA KEV+300.0EPSS percentile 46.3.463 × 209.3No public exploit+100.0SSVC exploitation: none+100.0
Description · from the CVE record

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

ProductAffectedFixed inSource
Crypt::NaCl::Sodium≤ 2.002–CNA

Scores by source

CISA ADP9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CISA ADPSSVCExploitation: none · Automatable: yes · Technical impact: total

References

refmetacpan.org/release/TIMLEGGE/Crypt-NaCl-Sodium-2.002/source/Sodium.xs#L2116refmetacpan.org/release/TIMLEGGE/Crypt-NaCl-Sodium-2.002/source/Sodium.xs#L2310refmetacpan.org/release/TIMLEGGE/Crypt-NaCl-Sodium-2.002/source/Sodium.xs#L3304refmetacpan.org/release/TIMLEGGE/Crypt-NaCl-Sodium-2.002/source/Sodium.xs#L942patchgithub.com/cpan-authors/crypt-nacl-sodium/pull/24.patchrefmetacpan.org/release/TIMLEGGE/Crypt-NaCl-Sodium-2.003/source/Changesrefopenwall.com/lists/oss-security/2026/03/08/1