CVE-2026-102483 Reachable Assertion in ntpsec
High 7.5
Published
Updated
Check this codebase for CVE-2026-102483 and fix it if it is affected.
What it is: CVE-2026-102483 is a high-severity vulnerability in ntpsec, published on 21 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-102483 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-102483/ (Markdown: https://insights.sbomify.com/CVE-2026-102483/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2026-102483?
CVE-2026-102483 is a high-severity vulnerability in ntpsec, published on 21 Oct 2026.
Official description
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.
Weakness: CWE-617
Which versions are affected by CVE-2026-102483?
How do I fix CVE-2026-102483?
Upgrade to a fixed version.
Is CVE-2026-102483 being exploited?
There is no known exploitation of CVE-2026-102483 in the wild and no public exploit code.
Sources
Also known as DEBIAN-CVE-2026-102483, GHSA-6xg3-q93h-wcgv, UBUNTU-CVE-2026-102483.