CVE-2026-30910 identifies an integer overflow vulnerability in the Crypt::Sodium::XS Perl module, specifically in versions through 0.001000. The vulnerability stems from the failure to validate that the output buffer sizes for combined AEAD encryption, combined signature creation, and bin2hex functions remain below the maximum allowable size (SIZE_MAX). When processing very large input messages, this can cause integer wraparound, resulting in undersized output buffers. For bin2hex and encryption algorithms other than aes256gcm, this leads to crashes due to buffer underrun or invalid memory access. For aes256gcm encryption and signature functions, the undersized buffer can cause buffer overflows, potentially allowing attackers to corrupt memory or execute arbitrary code. The input sizes required to trigger these conditions are extremely large (e.g., input size > SIZE_MAX / 2 for bin2hex, > SIZE_MAX - 32 for aegis encryption), making exploitation difficult in practice. No patches or fixes are currently linked, and no known exploits have been reported. The vulnerability is classified under CWE-190 (Integer Overflow or Wraparound).

The impact of CVE-2026-30910 includes potential denial of service through application crashes and, more critically, memory corruption via buffer overflows in aes256gcm encryption and signature functions. This can compromise confidentiality and integrity of cryptographic operations, potentially allowing attackers to bypass security guarantees or execute arbitrary code if exploited. Although exploitation requires very large input sizes, systems processing large volumes of data or untrusted inputs could be at risk. Organizations relying on Crypt::Sodium::XS for cryptographic functions in Perl applications, especially those handling sensitive data or operating in security-critical environments, could face service disruption or data compromise. The absence of known exploits reduces immediate risk, but the vulnerability's presence in cryptographic primitives elevates its potential severity.

Organizations should monitor for official patches or updates from the IAMB project and apply them promptly once available. In the interim, developers should implement strict input validation to limit message sizes well below thresholds that could trigger integer overflow conditions. Code audits should verify that all buffer size calculations properly check for integer overflows and respect SIZE_MAX limits. Employing fuzz testing and static analysis tools focused on integer overflow detection can help identify similar issues. Where feasible, consider using alternative, well-maintained cryptographic libraries without this vulnerability. Additionally, runtime protections such as AddressSanitizer or similar memory safety tools can help detect and mitigate exploitation attempts during development and testing phases.