LiveActive security incident?Get immediate response
CVE Record

CVE-2026-21905: Junos OS: SRX Series, MX Series with MX-SPC3 or MS-MPC: Receipt of multiple specific SIP messages results in flow management process crash

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.

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeHuman-supervisedhigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-21905 can let an unauthenticated attacker crash traffic-handling processes on affected Juniper SRX and certain MX devices by sending multiple crafted SIP messages over TCP. The business impact is denial of service, potentially disrupting firewall or service-card traffic handling. Juniper lists fixed Junos OS releases.

Executive priority

Treat as a high-priority availability risk for exposed Juniper security and service-edge infrastructure. Patch planning should focus first on devices handling SIP-over-TCP or providing critical network paths.

Technical view

The flaw is a CWE-835 infinite loop in the Junos OS SIP ALG. On SRX and MX with MX-SPC3 or MS-MPC, multiple SIP-over-TCP messages can be parsed incorrectly, causing watchdog expiration and crashing flowd or mspmand. SIP over UDP is not affected. CVSS v4.0 score is 8.7.

Likely exposure

Exposure is limited to Juniper SRX Series and MX Series using MX-SPC3 or MS-MPC service cards, running affected Junos OS versions, with SIP-over-TCP traffic reaching the SIP ALG path.

Exploitation context

The advisory describes unauthenticated network-based exploitation with low attack complexity. The source bundle does not indicate known active exploitation, and the CVE is not marked KEV. No public exploit status is provided in the supplied sources.

Researcher notes

Do not assume UDP SIP exposure is relevant; Juniper states only TCP triggers the issue. Evidence is vendor-advisory based. The supplied data does not name workarounds beyond upgrading to fixed Junos OS releases or consulting vendor guidance.

Mitigation direction

  • Upgrade affected Junos OS devices to the fixed releases listed by Juniper.
  • Prioritize SRX and MX devices processing SIP-over-TCP traffic.
  • Check Juniper advisory JSA106004 for current remediation guidance.
  • If immediate upgrade is not possible, consult Juniper for supported compensating controls.

Validation and detection

  • Inventory SRX Series and MX Series devices with MX-SPC3 or MS-MPC cards.
  • Compare installed Junos OS versions against Juniper’s affected and fixed version ranges.
  • Confirm whether SIP-over-TCP traffic can reach the SIP ALG path.
  • Review device logs for flowd or mspmand crashes consistent with the advisory.
Prepared
Editorial supervisor
Michael Williams
Confidence
high
Sources
4

Automatically approved under Michael Williams's editorial policy. This source version was not individually reviewed.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-835: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-21905 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.7 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/AU:Y/R:A/V:C/RE:M/U:Amber

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.7CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/AU:Y/R:A/V:C/RE:M/U:Amber——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.7High
CVSS 4.0 vector shape for CVE-2026-21905Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/AU:Y/R:A/V:C/RE:M/U:Amber

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Juniper NetworksJunos OS0, 21.4, 22.4, 23.2, 23.4, 24.2, 24.4, 25.2unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-835 · source CWE mapping

Loop with Unreachable Exit Condition ('Infinite Loop')

Loop with Unreachable Exit Condition ('Infinite Loop') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.