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-21905: CWE-835 Loop with Unreachable Exit Condition ('Infinite Loop') in Juniper Networks Junos OS

0
High
VulnerabilityCVE-2026-21905cvecve-2026-21905cwe-835
Published: Thu Jan 15 2026 (01/15/2026, 20:19:22 UTC)
Source: CVE Database V5
Vendor/Project: Juniper Networks
Product: Junos OS

Description

CVE-2026-21905 is a high-severity vulnerability in Juniper Networks Junos OS affecting SRX Series and MX Series devices with MX-SPC3 or MS-MPC service cards. It involves an infinite loop triggered by malformed SIP messages over TCP, causing the flow management process to crash and resulting in a denial of service (DoS). The vulnerability requires no authentication or user interaction and affects multiple Junos OS versions prior to specific patched releases. SIP messages over UDP are not affected. Exploitation leads to a crash of critical processes (flowd or mspmand), disrupting network traffic handling. No known exploits are currently reported in the wild. European organizations relying on Juniper SRX or MX Series devices for network security and routing are at risk of service disruption. Mitigation requires timely patching to the fixed Junos OS versions. Network-level filtering of SIP TCP traffic and monitoring for anomalous SIP message patterns can reduce exposure. Countries with high adoption of Juniper infrastructure and critical telecom or enterprise networks are most likely impacted.

AI-Powered Analysis

AILast updated: 01/22/2026, 21:26:33 UTC

Technical Analysis

CVE-2026-21905 is a vulnerability classified under CWE-835 (Loop with Unreachable Exit Condition) found in the SIP application layer gateway (ALG) component of Juniper Networks Junos OS running on SRX Series and MX Series routers equipped with MX-SPC3 or MS-MPC service cards. The flaw arises when the device receives multiple SIP messages over TCP; the SIP headers are parsed incorrectly, causing the processing loop to become infinite. This infinite loop leads to the expiration of a watchdog timer, which in turn crashes the flow management process—specifically, the flowd process on SRX Series and MX Series with MX-SPC3 cards, or the mspmand process on MX Series with MS-MPC cards. The crash results in a denial of service (DoS) condition, disrupting the device's ability to manage network flows. The vulnerability is exploitable remotely without authentication or user interaction, making it accessible to unauthenticated network-based attackers who can send crafted SIP messages over TCP. Notably, SIP messages over UDP do not trigger this issue. The affected Junos OS versions span multiple releases before the patched versions 21.2R3-S10, 21.4R3-S12, 22.4R3-S8, 23.2R2-S5, 23.4R2-S6, 24.2R2-S3, 24.4R2-S1, and 25.2R1-S1/25.2R2. Although no known exploits are reported in the wild, the vulnerability's characteristics and ease of exploitation make it a significant risk for network availability. The root cause is improper SIP header parsing leading to an infinite loop, a classic denial of service vector in network protocol handling components.

Potential Impact

For European organizations, the impact of CVE-2026-21905 can be substantial, especially for those relying on Juniper SRX and MX Series devices for critical network security and routing functions. The denial of service caused by crashing flow management processes can lead to network outages, degraded performance, and loss of connectivity for enterprise and service provider networks. This disruption can affect business operations, critical communications, and service availability. Telecommunications providers using Juniper MX Series routers with affected service cards may experience service interruptions impacting large customer bases. Enterprises with SRX Series firewalls may face security gaps during downtime, increasing exposure to other threats. The vulnerability’s unauthenticated, network-based exploit vector means attackers can launch attacks remotely without prior access, increasing the risk of widespread disruption. Given the importance of these devices in network infrastructure, the potential for cascading effects on dependent services and applications is significant. Additionally, the inability to handle SIP traffic properly may affect VoIP and unified communications systems that rely on SIP, further impacting business communications.

Mitigation Recommendations

The primary mitigation is to apply the vendor-provided patches by upgrading affected Junos OS versions to the fixed releases listed: 21.2R3-S10 or later, 21.4R3-S12 or later, 22.4R3-S8 or later, 23.2R2-S5 or later, 23.4R2-S6 or later, 24.2R2-S3 or later, 24.4R2-S1 or later, and 25.2R1-S1/25.2R2 or later. Until patches can be applied, organizations should implement network-level controls to limit exposure. This includes filtering or rate-limiting SIP traffic over TCP at network perimeters and ingress points, especially from untrusted sources. Monitoring SIP traffic for abnormal patterns or excessive malformed messages can help detect exploitation attempts early. Disabling SIP ALG functionality on affected devices, if feasible without impacting business operations, can reduce attack surface. Employing intrusion detection/prevention systems (IDS/IPS) with signatures targeting malformed SIP TCP messages may provide additional protection. Regularly auditing device configurations and ensuring minimal exposure of management interfaces to untrusted networks is recommended. Finally, organizations should prepare incident response plans to quickly address potential DoS events caused by this vulnerability.

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

Threat ID: 69694e761ab3796b1050010a

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

Last enriched: 1/22/2026, 9:26:33 PM

Last updated: 2/6/2026, 11:55:04 AM

Views: 52

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