CVE-2026-30910
Crypt::Sodium::XS versions through 0.001000 for Perl has potential integer overflows
Crypt::Sodium::XS versions through 0.001000 for Perl has potential integer overflows. Combined aead encryption, combined signature creation, and bin2hex functions do not check that output size will be less than SIZE_MAX, which could lead to integer wraparound causing an undersized output buffer. This can cause a crash in bin2hex and encryption algorithms other than aes256gcm. For aes256gcm encryption and signatures, an undersized buffer could lead to buffer overflow. Encountering this issue is unlikely as the message length would need to be very large. For bin2hex the input size would have to be > SIZE_MAX / 2 For aegis encryption the input size would need to be > SIZE_MAX - 32U For other encryption the input size would need to be > SIZE_MAX - 16U For signatures the input size would need to be > SIZE_MAX - 64U
| CWE | CWE-190 |
| Vendor | iamb |
| Product | crypt::sodium::xs |
| Published | Mar 8, 2026 |
| Last Updated | Mar 10, 2026 |
Get instant alerts for iamb crypt::sodium::xs
Be the first to know when new high vulnerabilities affecting iamb crypt::sodium::xs are published — delivered to Slack, Telegram or Discord.