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-21921: CWE-416 Use After Free in Juniper Networks Junos OS

0
Medium
VulnerabilityCVE-2026-21921cvecve-2026-21921cwe-416
Published: Thu Jan 15 2026 (01/15/2026, 20:28:29 UTC)
Source: CVE Database V5
Vendor/Project: Juniper Networks
Product: Junos OS

Description

CVE-2026-21921 is a Use After Free vulnerability in the chassis daemon (chassisd) of Juniper Networks Junos OS and Junos OS Evolved. It allows a network-based attacker with low privileges to cause a denial-of-service (DoS) by triggering crashes in telemetry-capable processes through frequent subscription and unsubscription to sensors. Affected versions include all Junos OS and Junos OS Evolved releases prior to 22. 4R3-S8, 23. 2R2-S5, and 23. 4R2. The vulnerability results in process crashes and restarts, potentially causing complete outages until recovery. The CVSS score is 6. 5 (medium severity), reflecting no confidentiality or integrity impact but high availability impact. No known exploits are currently reported in the wild.

AI-Powered Analysis

AILast updated: 01/22/2026, 21:38:32 UTC

Technical Analysis

CVE-2026-21921 is a Use After Free vulnerability classified under CWE-416 found in the chassis daemon (chassisd) component of Juniper Networks Junos OS and Junos OS Evolved. The flaw arises when telemetry collectors frequently subscribe and unsubscribe to sensors over extended periods, causing memory management errors that lead to use-after-free conditions. This triggers crashes in telemetry-capable processes including chassisd, rpd, and mib2d. These crashes cause the affected processes to restart, which depending on the process, can lead to partial or complete network outages until recovery is complete. The vulnerability requires network access and low-privilege authentication but does not require user interaction. It affects all versions before 22.4R3-S8, 23.2 versions before 23.2R2-S5, and 23.4 versions before 23.4R2 for both Junos OS and Junos OS Evolved. The CVSS v3.1 score is 6.5, indicating a medium severity primarily due to the high impact on availability (denial of service) without affecting confidentiality or integrity. No public exploits have been reported yet, but the vulnerability could be leveraged to disrupt network operations by causing repeated process crashes. Juniper has released patches in the specified fixed versions to address this issue.

Potential Impact

The primary impact of CVE-2026-21921 is denial-of-service caused by crashes and restarts of critical telemetry processes on Juniper network devices. For European organizations, this can translate into network outages, degraded performance, or loss of telemetry data critical for network monitoring and management. Organizations relying heavily on Juniper routers and switches for core networking, especially those using telemetry for real-time monitoring, risk operational disruptions. This can affect ISPs, financial institutions, government agencies, and large enterprises with complex network infrastructures. The downtime caused by process crashes can lead to service interruptions, impacting business continuity and potentially violating regulatory uptime requirements. Since the vulnerability requires low-privilege authentication, insider threats or compromised credentials could be exploited to trigger the DoS. The lack of confidentiality or integrity impact reduces risks of data breaches but availability loss remains a significant concern.

Mitigation Recommendations

1. Upgrade affected Junos OS and Junos OS Evolved devices to the fixed versions: 22.4R3-S8 or later, 23.2R2-S5 or later, and 23.4R2 or later. 2. Limit the frequency of telemetry subscription and unsubscription requests to reduce the risk of triggering the use-after-free condition. 3. Implement strict access controls and monitoring on network management interfaces to prevent unauthorized or low-privilege users from abusing telemetry subscription mechanisms. 4. Monitor telemetry-capable processes (chassisd, rpd, mib2d) for abnormal crashes or restarts and establish alerting to respond quickly to potential exploitation attempts. 5. Employ network segmentation and least privilege principles to restrict access to Juniper device management interfaces. 6. Regularly audit and rotate credentials used for device management to mitigate risks from compromised accounts. 7. Engage with Juniper support and subscribe to security advisories for timely updates and patches.

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.712Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 696951f81ab3796b10539d01

Added to database: 1/15/2026, 8:45:44 PM

Last enriched: 1/22/2026, 9:38:32 PM

Last updated: 2/7/2026, 11:22:22 AM

Views: 127

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