# CVE-2026-121506: Out-of-bounds Write in NTPsec


- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 3 Nov 2026
- **Updated:** 3 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-121506, GHSA-28fm-m2x6-h5pf, UBUNTU-CVE-2026-121506

## What is CVE-2026-121506?

CVE-2026-121506 is a high-severity vulnerability in NTPsec, published on 3 Nov 2026. 

### Official description

An out-of-bounds read and write in NTS client extension field parsing (extens_client_recv) in NTPsec before 1.2.5 allows a remote attacker who can send NTP server-mode replies to an NTS client to corrupt heap memory and crash ntpd, and, combined with the NTS-KE client out-of-bounds read fixed in 1.2.4, to bypass NTS authentication and set the client's time, via an NTS Authenticator and Encrypted Extension Fields field whose nonce length exceeds the field.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

Upgrade to a fixed version.

## Is CVE-2026-121506 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121506 is a high-severity vulnerability in NTPsec, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121506 in the wild and no public exploit code.

Affected product: NTPsec. 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-121506/ (Markdown: https://insights.sbomify.com/CVE-2026-121506/index.md)
```

## Sources

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

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