CVE-2026-102080
CVE-2026-102080 is a medium-severity vulnerability with a CVSS 3.x base score of 5.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-413.
Key facts
- Severity: Medium (CVSS 3.x base score 5.3)
- CVSS v4: 6.0
- EPSS exploit prediction: 0% (8th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-413
- Published:
- Last modified:
Description
An Improper Resource Locking vulnerability in the clock synchronization daemon (clksyncd) of Juniper Networks Junos OS on MX Series allows a unauthenticated, logically adjacent attacker to cause a Denial-of-Service (DoS). If a SyncE or PTP upstream node sends a malformed message to an MX device equipped with SCBE3, a false 19.44MHz alarm is generated on the master RE. This leads to persistent RE switchovers and a clksyncd process crash. This issue is outside the attacker's direct control as it's a race condition. This issue affects Junos OS on MX Series: * All versions before 23.2R2-S7.7; * 23.4 versions before 23.4R2-S8.13; * 24.2 versions before 24.2R2-S5.5; * 24.4 versions before 24.4R2-S4; * 25.2 versions before 25.2R2-S1; * 25.4 versions before 25.4R1-S2.
Frequently asked questions
- What is CVE-2026-102080?
- An Improper Resource Locking vulnerability in the clock synchronization daemon (clksyncd) of Juniper Networks Junos OS on MX Series allows a unauthenticated, logically adjacent attacker to cause a Denial-of-Service (DoS). If a SyncE or PTP upstream node sends a malformed message to an MX device equipped with SCBE3, a false 19.44MHz alarm is generated on the master RE. This leads to persistent RE switchovers and a clksyncd process crash. This issue is outside the attacker's direct control as it's a race condition. This issue affects Junos OS on MX Series: * All versions before 23.2R2-S7.7; * 23.4 versions before 23.4R2-S8.13; * 24.2 versions before 24.2R2-S5.5; * 24.4 versions before 24.4R2-S4; * 25.2 versions before 25.2R2-S1; * 25.4 versions before 25.4R1-S2.
- How severe is CVE-2026-102080?
- CVE-2026-102080 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over an adjacent network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
- Is CVE-2026-102080 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (8th percentile), an estimate of the probability of exploitation in the next 30 days.
- How do I fix CVE-2026-102080?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2026-102080 published?
- CVE-2026-102080 was published on 2026-10-14 and last updated on 2026-10-15.
References
Other CWE-413 vulnerabilities
- CVE-2025-3450 — Critical (CVSS 10.0): An Improper Resource Locking vulnerability in the SDM component of B&R Automation Runtime versions before 6.3 and…
- CVE-2026-48178 — High (CVSS 8.8): Out of bound access in PPC due to race condition in global variable access
- CVE-2023-28649 — High (CVSS 8.6): The Hub in the Snap One OvrC cloud platform is a device used to centralize and manage nested devices connected to it. A…
- CVE-2019-8998 — High (CVSS 7.8): An information disclosure vulnerability leading to a potential local escalation of privilege in the procfs service (the…
- CVE-2022-49737 — High (CVSS 7.7): In X.Org X server 20.11 through 21.1.16, when a client application uses easystroke for mouse gestures, the main thread…
- CVE-2026-32748 — High (CVSS 7.5): Squid is a caching proxy for the Web. Prior to version 7.5, due to premature release of resource during expected…