CVE-2026-102080: CWE-413 Improper Resource Locking in Juniper Networks Junos OS
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.
CVSS v3.1
Score 5.3medium
Affected software
Juniper Networks
Junos OS
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability (CWE-413) in Juniper Networks Junos OS affects the clock synchronization daemon (clksyncd) on MX Series devices equipped with SCBE3. When a SyncE or PTP upstream node sends a malformed message, a false 19.44MHz alarm is generated on the master route engine, causing persistent route engine switchovers and clksyncd process crashes. The vulnerability arises from improper resource locking leading to a race condition. It can be exploited by an unauthenticated, logically adjacent attacker to cause denial-of-service. Affected versions include all Junos OS releases before 23.2R2-S7.7, certain 23.4, 24.2, 24.4, 25.2, and 25.4 versions prior to their respective fixed releases.
Potential Impact
The vulnerability allows an unauthenticated attacker with logical adjacency to cause denial-of-service on MX Series devices by triggering persistent route engine switchovers and crashes of the clksyncd process. There is no impact on confidentiality or integrity, only availability is affected.
Mitigation Recommendations
A fix is available in Junos OS versions 23.2R2-S7.7 and later for the 23.2 release train, 23.4R2-S8.13 and later for 23.4, 24.2R2-S5.5 and later for 24.2, 24.4R2-S4 and later for 24.4, 25.2R2-S1 and later for 25.2, and 25.4R1-S2 and later for 25.4. Users should upgrade to these fixed versions to remediate the vulnerability. No other mitigation or workaround is indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- juniper
- Date Reserved
- 2026-09-28T17:37:38.548Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6acfb2fa2cdf04f65696236a
Added to database: 10/14/2026, 16:51:06 UTC
Last enriched: 10/14/2026, 17:03:59 UTC
Last updated: 10/14/2026, 22:28:18 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.