Monitor vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.8

Perl's Crypt::NaCl::Sodium may produce too-small encryption outputs

CVE-2026-30909
Summary

Perl's Crypt::NaCl::Sodium library for encryption may produce smaller-than-expected results if the input data is extremely large. This is unlikely to happen in normal use, but if it does, it could lead to errors or data corruption. Users should consider upgrading to version 2.003 or later to fix this issue.

Original title
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 ...
Original 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
Vulnerability type
CWE-190 Integer Overflow
Published: 8 Mar 2026 · Updated: 13 Mar 2026 · First seen: 8 Mar 2026