ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-30909

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

Published Mar 8, 2026 · catalog updated Jun 17, 2026 · Crypt::NaCl::Sodium versions through 2.002

Check if you run it

No confirmed exploitation is on record for CVE-2026-30909. EPSS is 0.78%. Act only if a listed version of Crypt::NaCl::Sodium versions through 2.002 is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Crypt::NaCl::Sodium versions through 2.002).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Critical9.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.78%
Remediation
Advisory link
Affected products
cpe timlegge/crypt

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

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe timlegge/crypt\

How to fix CVE-2026-30909

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-30909. EPSS is 0.78%. Act only if a listed version of Crypt::NaCl::Sodium versions through 2.002 is installed.

Which versions are affected?

Compare what you have installed with \. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-190: Integer Overflow. EPSS 0.78%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 8, 2026 · NIST NVD

    Detected

    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

  2. Jun 17, 2026 · NIST NVD

    Updated

    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

Sources

  • CVE.orgVulnerability recordCVE-2026-30909

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-30909

    30-day exploitation probability 0.8%

    first.org
  • NIST NVDVulnerability recordCVE-2026-30909

    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 buffe

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.