CVE-2026-21905: CWE-835 Loop with Unreachable Exit Condition ('Infinite Loop') in Juniper Networks Junos OS
A Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in the SIP application layer gateway (ALG) of Juniper Networks Junos OS on SRX Series and MX Series with MX-SPC3 or MS-MPC allows an unauthenticated network-based attacker sending specific SIP messages over TCP to crash the flow management process, leading to a Denial of Service (DoS). On SRX Series, and MX Series with MX-SPC3 or MS-MPC service cards, receipt of multiple SIP messages causes the SIP headers to be parsed incorrectly, eventually causing a continuous loop and leading to a watchdog timer expiration, crashing the flowd process on SRX Series and MX Series with MX-SPC3, or mspmand process on MX Series with MS-MPC. This issue only occurs over TCP. SIP messages sent over UDP cannot trigger this issue. This issue affects Junos OS on SRX Series and MX Series with MX-SPC3 and MS-MPC: * all versions before 21.2R3-S10, * from 21.4 before 21.4R3-S12, * from 22.4 before 22.4R3-S8, * from 23.2 before 23.2R2-S5, * from 23.4 before 23.4R2-S6, * from 24.2 before 24.2R2-S3, * from 24.4 before 24.4R2-S1, * from 25.2 before 25.2R1-S1, 25.2R2.
AI Analysis
Technical Summary
CVE-2026-21905 is a vulnerability classified under CWE-835 (Loop with Unreachable Exit Condition) found in the SIP application layer gateway (ALG) of Juniper Networks Junos OS running on SRX Series and MX Series devices equipped with MX-SPC3 or MS-MPC service cards. The flaw arises when the SIP ALG improperly parses multiple SIP messages sent over TCP, causing the SIP headers to be misinterpreted and triggering an infinite loop within the flow management process. This loop leads to the expiration of a watchdog timer, which forcibly crashes 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 vulnerability is exploitable remotely by an unauthenticated attacker who can send crafted SIP messages over TCP, without requiring any user interaction. This results in a denial of service (DoS) condition by disrupting critical flow management processes that handle network traffic. The issue affects a broad range of Junos OS versions prior to the patched releases starting from 21.2R3-S10 and continuing through multiple subsequent versions up to 25.2R2. The vulnerability does not affect SIP messages sent over UDP, limiting the attack vector to TCP-based SIP traffic. Although no exploits have been observed in the wild yet, the vulnerability's characteristics—remote, unauthenticated, no user interaction, and high impact on availability—make it a significant risk for network operators using affected Juniper devices. Juniper has published patches in the indicated versions to address this issue.
Potential Impact
The primary impact of CVE-2026-21905 is a denial of service condition caused by crashing critical flow management processes on Juniper SRX and MX Series devices. For European organizations, especially those relying on Juniper devices for perimeter security, routing, or session management in their networks, this vulnerability could lead to significant network outages or degraded service availability. Disruption of flowd or mspmand processes can interrupt traffic inspection, firewalling, and routing functions, potentially causing widespread connectivity issues. This is particularly critical for telecommunications providers, financial institutions, government agencies, and enterprises with high availability requirements. The vulnerability does not expose confidentiality or integrity risks directly but can be leveraged as part of a larger attack to degrade network defenses or cause operational disruption. Given the widespread use of Juniper devices in Europe’s telecom and enterprise sectors, the potential for service interruption is notable. The lack of authentication requirement and ease of triggering the flaw over TCP increases the risk of exploitation from both external attackers and insider threats. However, the attack vector is limited to SIP traffic over TCP, which may reduce exposure in environments where SIP is not used or is segregated.
Mitigation Recommendations
To mitigate CVE-2026-21905, European organizations should prioritize upgrading affected Juniper Junos OS devices to the fixed versions starting from 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 or later as applicable. Until patches can be applied, organizations should implement network-level controls to limit exposure to malicious SIP TCP traffic. This includes deploying firewall rules or access control lists (ACLs) to restrict SIP traffic to trusted sources and segregating SIP traffic from critical network infrastructure. Monitoring and alerting on abnormal SIP message patterns or repeated flowd/mspmand process crashes can provide early detection of exploitation attempts. Additionally, disabling SIP ALG functionality on Juniper devices where it is not required can reduce the attack surface. Network segmentation to isolate SIP traffic and employing intrusion prevention systems (IPS) with signatures targeting malformed SIP messages can further mitigate risk. Regularly reviewing device logs and flow management process health is recommended to detect potential exploitation. Organizations should also engage with Juniper support for guidance and verify that all devices are running supported and patched software versions.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Poland, Sweden, Belgium, Finland
CVE-2026-21905: CWE-835 Loop with Unreachable Exit Condition ('Infinite Loop') in Juniper Networks Junos OS
Description
A Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in the SIP application layer gateway (ALG) of Juniper Networks Junos OS on SRX Series and MX Series with MX-SPC3 or MS-MPC allows an unauthenticated network-based attacker sending specific SIP messages over TCP to crash the flow management process, leading to a Denial of Service (DoS). On SRX Series, and MX Series with MX-SPC3 or MS-MPC service cards, receipt of multiple SIP messages causes the SIP headers to be parsed incorrectly, eventually causing a continuous loop and leading to a watchdog timer expiration, crashing the flowd process on SRX Series and MX Series with MX-SPC3, or mspmand process on MX Series with MS-MPC. This issue only occurs over TCP. SIP messages sent over UDP cannot trigger this issue. This issue affects Junos OS on SRX Series and MX Series with MX-SPC3 and MS-MPC: * all versions before 21.2R3-S10, * from 21.4 before 21.4R3-S12, * from 22.4 before 22.4R3-S8, * from 23.2 before 23.2R2-S5, * from 23.4 before 23.4R2-S6, * from 24.2 before 24.2R2-S3, * from 24.4 before 24.4R2-S1, * from 25.2 before 25.2R1-S1, 25.2R2.
AI-Powered Analysis
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) of Juniper Networks Junos OS running on SRX Series and MX Series devices equipped with MX-SPC3 or MS-MPC service cards. The flaw arises when the SIP ALG improperly parses multiple SIP messages sent over TCP, causing the SIP headers to be misinterpreted and triggering an infinite loop within the flow management process. This loop leads to the expiration of a watchdog timer, which forcibly crashes 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 vulnerability is exploitable remotely by an unauthenticated attacker who can send crafted SIP messages over TCP, without requiring any user interaction. This results in a denial of service (DoS) condition by disrupting critical flow management processes that handle network traffic. The issue affects a broad range of Junos OS versions prior to the patched releases starting from 21.2R3-S10 and continuing through multiple subsequent versions up to 25.2R2. The vulnerability does not affect SIP messages sent over UDP, limiting the attack vector to TCP-based SIP traffic. Although no exploits have been observed in the wild yet, the vulnerability's characteristics—remote, unauthenticated, no user interaction, and high impact on availability—make it a significant risk for network operators using affected Juniper devices. Juniper has published patches in the indicated versions to address this issue.
Potential Impact
The primary impact of CVE-2026-21905 is a denial of service condition caused by crashing critical flow management processes on Juniper SRX and MX Series devices. For European organizations, especially those relying on Juniper devices for perimeter security, routing, or session management in their networks, this vulnerability could lead to significant network outages or degraded service availability. Disruption of flowd or mspmand processes can interrupt traffic inspection, firewalling, and routing functions, potentially causing widespread connectivity issues. This is particularly critical for telecommunications providers, financial institutions, government agencies, and enterprises with high availability requirements. The vulnerability does not expose confidentiality or integrity risks directly but can be leveraged as part of a larger attack to degrade network defenses or cause operational disruption. Given the widespread use of Juniper devices in Europe’s telecom and enterprise sectors, the potential for service interruption is notable. The lack of authentication requirement and ease of triggering the flaw over TCP increases the risk of exploitation from both external attackers and insider threats. However, the attack vector is limited to SIP traffic over TCP, which may reduce exposure in environments where SIP is not used or is segregated.
Mitigation Recommendations
To mitigate CVE-2026-21905, European organizations should prioritize upgrading affected Juniper Junos OS devices to the fixed versions starting from 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 or later as applicable. Until patches can be applied, organizations should implement network-level controls to limit exposure to malicious SIP TCP traffic. This includes deploying firewall rules or access control lists (ACLs) to restrict SIP traffic to trusted sources and segregating SIP traffic from critical network infrastructure. Monitoring and alerting on abnormal SIP message patterns or repeated flowd/mspmand process crashes can provide early detection of exploitation attempts. Additionally, disabling SIP ALG functionality on Juniper devices where it is not required can reduce the attack surface. Network segmentation to isolate SIP traffic and employing intrusion prevention systems (IPS) with signatures targeting malformed SIP messages can further mitigate risk. Regularly reviewing device logs and flow management process health is recommended to detect potential exploitation. Organizations should also engage with Juniper support for guidance and verify that all devices are running supported and patched software versions.
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/15/2026, 8:46:09 PM
Last updated: 1/15/2026, 11:13:09 PM
Views: 4
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-2025-68671: CWE-294: Authentication Bypass by Capture-replay in treeverse lakeFS
MediumCVE-2026-1009: CWE-79 Improper Neutralization of Input During Web Page Generation (Cross-site Scripting) in Altium Altium Forum (Altium 365)
CriticalCVE-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
UnknownActions
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.