CVE-2026-21921: CWE-416 Use After Free in Juniper Networks Junos OS
A Use After Free vulnerability in the chassis daemon (chassisd) of Juniper Networks Junos OS and Junos OS Evolved allows a network-based attacker authenticated with low privileges to cause a Denial-of-Service (DoS). When telemetry collectors are frequently subscribing and unsubscribing to sensors continuously over a long period of time, telemetry-capable processes like chassisd, rpd or mib2d will crash and restart, which - depending on the process - can cause a complete outage until the system has recovered. This issue affects: Junos OS: * all versions before 22.4R3-S8, * 23.2 versions before 23.2R2-S5, * 23.4 versions before 23.4R2; Junos OS Evolved: * all versions before 22.4R3-S8-EVO, * 23.2 versions before 23.2R2-S5-EVO, * 23.4 versions before 23.4R2-EVO.
AI Analysis
Technical Summary
CVE-2026-21921 is a Use After Free vulnerability classified under CWE-416, affecting the chassis daemon (chassisd) in Juniper Networks Junos OS and Junos OS Evolved. The flaw arises when telemetry collectors subscribe and unsubscribe repeatedly to sensors over extended periods, causing memory management errors that lead to process crashes. Specifically, processes responsible for telemetry and network management such as chassisd, rpd (routing protocol daemon), and mib2d (SNMP daemon) may crash and restart. Depending on which process crashes, this can cause partial or complete network outages until the system recovers. The vulnerability requires an attacker to be authenticated with low privileges and to have network access to the affected device. It does not require user interaction and does not impact confidentiality or integrity, but it severely impacts availability. Affected versions include all Junos OS releases before 22.4R3-S8, 23.2 versions before 23.2R2-S5, and 23.4 versions before 23.4R2, as well as corresponding Junos OS Evolved versions. The vulnerability was published on January 15, 2026, with a CVSS v3.1 score of 6.5, indicating a medium severity level. No public exploits have been reported yet, but the nature of the vulnerability means that persistent telemetry subscription activity could be weaponized to cause denial-of-service conditions on critical network infrastructure.
Potential Impact
For European organizations, this vulnerability poses a significant risk to network availability, particularly for those relying on Juniper Networks devices for telemetry, routing, and network management. A successful exploitation could cause critical network daemons to crash and restart, leading to service outages that disrupt business operations, especially in sectors like telecommunications, finance, and government where network uptime is crucial. The DoS impact could affect data center connectivity, inter-office communications, and cloud service access. Since the vulnerability requires only low-privilege authenticated access, insider threats or compromised low-level accounts could be leveraged to trigger outages. The lack of confidentiality or integrity impact limits data breach risks, but availability disruptions could lead to operational downtime, financial losses, and reputational damage. Organizations with high telemetry subscription rates or automated monitoring systems may be more vulnerable to accidental triggering or targeted exploitation.
Mitigation Recommendations
European organizations should prioritize upgrading 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. Until patches are applied, network administrators should monitor telemetry subscription patterns to detect and limit frequent subscribe/unsubscribe activity that could trigger the vulnerability. Implement strict access controls to restrict low-privilege authenticated access to network devices, minimizing the risk of exploitation by unauthorized users. Employ network segmentation and monitoring to detect unusual telemetry traffic patterns indicative of exploitation attempts. Consider temporarily disabling telemetry subscription features if feasible or applying rate limiting on telemetry subscription requests. Regularly audit device logs for crashes or restarts of chassisd, rpd, or mib2d processes to identify early signs of exploitation. Coordinate with Juniper Networks support for guidance and updates. Finally, incorporate this vulnerability into incident response plans to ensure rapid recovery from potential DoS events.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Sweden, Poland
CVE-2026-21921: CWE-416 Use After Free in Juniper Networks Junos OS
Description
A Use After Free vulnerability in the chassis daemon (chassisd) of Juniper Networks Junos OS and Junos OS Evolved allows a network-based attacker authenticated with low privileges to cause a Denial-of-Service (DoS). When telemetry collectors are frequently subscribing and unsubscribing to sensors continuously over a long period of time, telemetry-capable processes like chassisd, rpd or mib2d will crash and restart, which - depending on the process - can cause a complete outage until the system has recovered. This issue affects: Junos OS: * all versions before 22.4R3-S8, * 23.2 versions before 23.2R2-S5, * 23.4 versions before 23.4R2; Junos OS Evolved: * all versions before 22.4R3-S8-EVO, * 23.2 versions before 23.2R2-S5-EVO, * 23.4 versions before 23.4R2-EVO.
AI-Powered Analysis
Technical Analysis
CVE-2026-21921 is a Use After Free vulnerability classified under CWE-416, affecting the chassis daemon (chassisd) in Juniper Networks Junos OS and Junos OS Evolved. The flaw arises when telemetry collectors subscribe and unsubscribe repeatedly to sensors over extended periods, causing memory management errors that lead to process crashes. Specifically, processes responsible for telemetry and network management such as chassisd, rpd (routing protocol daemon), and mib2d (SNMP daemon) may crash and restart. Depending on which process crashes, this can cause partial or complete network outages until the system recovers. The vulnerability requires an attacker to be authenticated with low privileges and to have network access to the affected device. It does not require user interaction and does not impact confidentiality or integrity, but it severely impacts availability. Affected versions include all Junos OS releases before 22.4R3-S8, 23.2 versions before 23.2R2-S5, and 23.4 versions before 23.4R2, as well as corresponding Junos OS Evolved versions. The vulnerability was published on January 15, 2026, with a CVSS v3.1 score of 6.5, indicating a medium severity level. No public exploits have been reported yet, but the nature of the vulnerability means that persistent telemetry subscription activity could be weaponized to cause denial-of-service conditions on critical network infrastructure.
Potential Impact
For European organizations, this vulnerability poses a significant risk to network availability, particularly for those relying on Juniper Networks devices for telemetry, routing, and network management. A successful exploitation could cause critical network daemons to crash and restart, leading to service outages that disrupt business operations, especially in sectors like telecommunications, finance, and government where network uptime is crucial. The DoS impact could affect data center connectivity, inter-office communications, and cloud service access. Since the vulnerability requires only low-privilege authenticated access, insider threats or compromised low-level accounts could be leveraged to trigger outages. The lack of confidentiality or integrity impact limits data breach risks, but availability disruptions could lead to operational downtime, financial losses, and reputational damage. Organizations with high telemetry subscription rates or automated monitoring systems may be more vulnerable to accidental triggering or targeted exploitation.
Mitigation Recommendations
European organizations should prioritize upgrading 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. Until patches are applied, network administrators should monitor telemetry subscription patterns to detect and limit frequent subscribe/unsubscribe activity that could trigger the vulnerability. Implement strict access controls to restrict low-privilege authenticated access to network devices, minimizing the risk of exploitation by unauthorized users. Employ network segmentation and monitoring to detect unusual telemetry traffic patterns indicative of exploitation attempts. Consider temporarily disabling telemetry subscription features if feasible or applying rate limiting on telemetry subscription requests. Regularly audit device logs for crashes or restarts of chassisd, rpd, or mib2d processes to identify early signs of exploitation. Coordinate with Juniper Networks support for guidance and updates. Finally, incorporate this vulnerability into incident response plans to ensure rapid recovery from potential DoS events.
Affected Countries
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/15/2026, 9:01:06 PM
Last updated: 1/15/2026, 10:43:44 PM
Views: 7
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.
Related Threats
CVE-2026-1008: CWE-79 Improper Neutralization of Input During Web Page Generation (Cross-site Scripting) in Altium Altium 365
MediumCVE-2026-0915: CWE-908 Use of Uninitialized Resource in The GNU C Library glibc
MediumCVE-2025-67822: n/a
UnknownCVE-2025-59959: CWE-822 Untrusted Pointer Dereference in Juniper Networks Junos OS
MediumCVE-2025-52987: CWE-1021 Improper Restriction of Rendered UI Layers or Frames in Juniper Networks Paragon Automation (Pathfinder, Planner, Insights)
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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.