cve.bz

CVE-2026-102483 ntpsec ntpsec: Reachable Assertion

7.5 highEPSS 0.4%

High (7.5) in ntpsec ntpsec. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Reachable exit in NTPsec ntpd 1.1.4 through 1.2.5 allows a remote attacker to terminate the daemon via an NTS request with excess NTS Cookie Placeholder extension fields.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 38th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-617 Reachable Assertion
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-102483 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-102483?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-102483?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-102483 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ntpsecfrom 1.1.4 before 1.2.6

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14ntpsecno fix listedDEBIAN-CVE-2026-102483
Ubuntu18.04:LTS, 20.04:LTS, 22.04:LTS and 3 morentpsecno fix listedUBUNTU-CVE-2026-102483
openSUSETumbleweedntpsec1.2.6-1.1openSUSE-SU-2026:12229-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important because remote, unauthenticated actors can induce an unexpected daemon crash without prior privileges or user interaction, resulting in a total denial of time synchronization services. Red Hat Enterprise Linux is unaffected by default because chrony serves as the standard NTP implementation, with NTPsec only distributed through optional community channels such as EPEL. Risk is therefore confined to deployments where NTPsec has been explicitly installed and exposed to untrusted network traffic, with no potential for code execution or unauthorized data access.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-102483.

References

Check your stackJSON