Skip to main content
VulnerabilityPublished

CVE-2026-121505: NTPsec · Out-of-bounds Read

Affects NTPsecSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.7 Low : upgrade to 1.2.4 when convenient.

Data as of 3 Nov 2026, 14:43 UTC

CVSS 3.1 base score
3.7Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitLab)CVSS 3.13.7
Patch
Available – fixed in 1.2.4
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

What to do

Upgrade NTPsec and ntpsec/ntpsec to 1.2.4.

Affected software

ProductAffectedFixed in
NTPsecNTPsecAffected
  • >=1.1.4 <1.2.4
Fixed in
  • 1.2.4
GitHubntpsec/ntpsecpkg:github/ntpsec/ntpsecOther threatsAffected
  • >=1.1.4 <1.2.4
Fixed in
  • 1.2.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade NTPsec to version 1.2.4 or later, where this vulnerability is fixed. No other mitigation is indicated or required.

Description

CVE-2026-121505 is an out-of-bounds read vulnerability in the NTS-KE client response parser of NTPsec versions 1.1.4 up to but not including 1.2.4. A malicious NTS-KE server can exploit this flaw to read the client's stack memory, including pointers that bypass ASLR protections. The leaked memory contents are then sent in cleartext as NTS cookies. This vulnerability has a low CVSS score of 3.7 and was fixed in version 1.2.4.

References

Community reviews

Loading reviews…