Quick answers
- Is CVE-2026-102484 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102484 being exploited in the wild.
- How severe is CVE-2026-102484?
- Medium severity, with a CVSS score of 6.4, published 21 October 2026.
- Which products and versions are affected?
- Ntpsec Ntpd before 1.2.6.
- Is there a fix for CVE-2026-102484?
- Yes: fixed in ntpd 1.2.6. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-102484 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-102484?
- Check whether you run Ntpsec Ntpd at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: ntpd 1.2.6
Technical details
The vulnerability is a heap-based buffer overflow in ntpd/refclock_jjy.c where the iTimestampCount variable could overflow when processing time replies from a JJY time source, exceeding the MAX_TIMESTAMP array bounds. An attacker controlling the Telephone JJY time source can trigger the overflow by sending more than six time replies, corrupting adjacent heap memory and crashing the ntpd process. The fix converts iTimestampCount to unsigned and adds bounds checking before incrementing the array index.
Affected products
- NTPsec ntpd before 1.2.6
Timeline
- 2026-10-21: disclosed
- 2026-09-29: patched: Fix commit 62a454f6 authored by Gary E. Miller