Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-21914: CWE-667 Improper Locking in Juniper Networks Junos OS

0
High
VulnerabilityCVE-2026-21914cvecve-2026-21914cwe-667
Published: Thu Jan 15 2026 (01/15/2026, 20:25:35 UTC)
Source: CVE Database V5
Vendor/Project: Juniper Networks
Product: Junos OS

Description

CVE-2026-21914 is a high-severity improper locking vulnerability in the GTP plugin of Juniper Networks Junos OS on SRX Series devices. An unauthenticated attacker can send a malformed GTP Modify Bearer Request message that causes a lock to be acquired and never released, leading to a watchdog timeout and FPC crash. This results in a denial-of-service condition causing complete traffic outage until the device recovers. The vulnerability affects multiple Junos OS versions prior to specific patched releases across versions 22. 4R3-S8 through 25. 2R2. Exploitation requires no authentication or user interaction and can be performed remotely over the network. There are no known exploits in the wild as of now. The CVSS v3. 1 score is 7.

AI-Powered Analysis

AILast updated: 01/22/2026, 21:39:12 UTC

Technical Analysis

CVE-2026-21914 is an improper locking vulnerability classified under CWE-667 found in the GPRS Tunnelling Protocol (GTP) plugin of Juniper Networks Junos OS running on SRX Series devices. The flaw arises when the device processes a specially crafted GTP Modify Bearer Request message. This malformed message causes the system to acquire a lock that is never released, effectively blocking other threads from obtaining the same lock. As a result, the device's internal watchdog timer triggers a timeout due to the lock contention, causing the Flexible PIC Concentrator (FPC) to crash and subsequently restart. This crash leads to a complete denial-of-service (DoS) condition, interrupting all traffic passing through the affected device until recovery is complete. The vulnerability affects a broad range of Junos OS versions, including all versions before 22.4R3-S8, 23.2 versions before 23.2R2-S5, 23.4 versions before 23.4R2-S6, 24.2 versions before 24.2R2-S3, 24.4 versions before 24.4R2-S2, and 25.2 versions before 25.2R1-S1 and 25.2R2. Exploitation requires no authentication or user interaction and can be performed remotely, making it a significant risk for network infrastructure relying on these devices. Although no public exploits have been reported yet, the vulnerability's nature and ease of exploitation warrant immediate attention. The CVSS v3.1 score of 7.5 reflects the high impact on availability with no confidentiality or integrity loss. Juniper has published patches in the specified versions to address this issue.

Potential Impact

For European organizations, this vulnerability poses a significant risk to network availability, especially for those relying on Juniper SRX Series devices as perimeter firewalls or core network security appliances. A successful exploit can cause a complete traffic outage, disrupting business operations, critical communications, and potentially impacting services dependent on continuous network connectivity. Sectors such as telecommunications, finance, government, and critical infrastructure operators are particularly vulnerable due to their reliance on stable and secure network infrastructure. The denial-of-service condition could lead to operational downtime, financial losses, and reputational damage. Additionally, the ease of exploitation without authentication increases the threat from opportunistic attackers or automated scanning tools. Given the widespread deployment of Juniper SRX devices in Europe, the potential scale of impact is considerable, especially if attackers target multiple devices simultaneously or leverage this vulnerability as part of a larger attack campaign.

Mitigation Recommendations

European organizations should immediately identify all Juniper SRX Series devices running affected Junos OS versions and prioritize patching to the fixed releases listed by Juniper Networks. Network administrators should apply the updates: 22.4R3-S8 or later, 23.2R2-S5 or later, 23.4R2-S6 or later, 24.2R2-S3 or later, 24.4R2-S2 or later, and 25.2R1-S1 or later. Until patches are applied, organizations should implement network-level mitigations such as filtering or rate-limiting GTP Modify Bearer Request messages from untrusted or external sources to reduce exposure. Monitoring network traffic for anomalous or malformed GTP messages can help detect attempted exploitation. Employing intrusion detection/prevention systems (IDS/IPS) with updated signatures targeting this vulnerability is recommended. Additionally, segmenting critical network infrastructure and restricting access to management interfaces can limit the attack surface. Regularly reviewing and updating incident response plans to include scenarios involving network device DoS is also advisable.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
juniper
Date Reserved
2026-01-05T17:32:48.711Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69694e771ab3796b1050015b

Added to database: 1/15/2026, 8:30:47 PM

Last enriched: 1/22/2026, 9:39:12 PM

Last updated: 2/7/2026, 12:35:16 PM

Views: 92

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats