# CVE-2026-30909: Crypt::NaCl::Sodium versions through 2.002 for Perl has potential integer overflows

> Integer overflows in Crypt::NaCl::Sodium functions may cause undersized buffers, potentially leading to crashes or memory issues with extremely large inputs.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Mar 2026
- **Updated:** 10 Mar 2026
- **Also known as:** GHSA-qqmj-w4wh-9w2h

## What is CVE-2026-30909?

CVE-2026-30909 is a critical vulnerability in TIMLEGGE Crypt::NaCl::Sodium, published on 8 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2026-30909?

It affects 1 product.


Products: Timlegge Crypt\.

## How do I fix CVE-2026-30909?

No fix has been published for CVE-2026-30909 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-30909 being exploited?

There is no known exploitation of CVE-2026-30909 in the wild and no public exploit code.

## Other vulnerabilities in TIMLEGGE Crypt::NaCl::Sodium

- [CVE-2026-2588](https://insights.sbomify.com/CVE-2026-2588/): Crypt::NaCl::Sodium versions through 2.001 for Perl has an integer overflow flaw on 32-bit systems (critical 9.1)
- [CVE-2025-1828](https://insights.sbomify.com/CVE-2025-1828/): Perl's Crypt::Random module after 1.05 and before 1.56 may use rand() function for cryptographic functions (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-30909 and fix it if it is affected.

What it is: CVE-2026-30909 is a critical vulnerability in TIMLEGGE Crypt::NaCl::Sodium, published on 8 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-30909 in the wild and no public exploit code.

Affected product: TIMLEGGE Crypt::NaCl::Sodium. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-30909/ (Markdown: https://insights.sbomify.com/CVE-2026-30909/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-30909
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-30909
- OSV: https://osv.dev/vulnerability/CVE-2026-30909

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-30909/
Summaries are generated and may contain mistakes; the official description above is the record.
