⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 7.5

How to Fix CVE-2026-21905: Denial of Service in Junos OS

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 7.5 - High
Actively exploited?Not currently listed in CISA KEV
Affected0 < 21.2R3-S10, 21.4 < 21.4R3-S12, 22.4 < 22.4R3-S8, 23.2 < 23.2R2-S5, 23.4 < 23.4R2-S6, 24.2 < 24.2R2-S3, and others
Fixed inSee vendor advisory
Type (CWE)CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop')

What is CVE-2026-21905?

CVE-2026-21905 is a denial of service flaw in Junos OS. A crafted request triggers a code path that crashes or hangs the service, taking the product offline for legitimate users. Vendor 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.

Why this CVE matters

Denial-of-service flaws in a network gateway or firewall have an outsize operational impact. A single packet that reboots an inline device takes down everything behind it, which is why even non-RCE bugs on these products warrant priority patching.

For deployments of Junos OS that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open Junos OS's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-21905

  1. Read the vendor advisory in full: https://supportportal.juniper.net/JSA106004
  2. Upgrade Junos OS to the patched build listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  5. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Junos OS CLI

_Verify the exact patched build against the vendor advisory: https://supportportal.juniper.net/JSA106004_


# Vendor advisory: https://supportportal.juniper.net/JSA106004
# 1. Confirm the running Junos release
show version | match "Junos"

# 2. Stage and install the patched package
request system software add /var/tmp/junos-<patched-version>.tgz no-validate reboot

# 3. After reboot
show version | match "Junos"

Verify the fix landed


# 1. Confirm the running version matches the patched build
#    (target per advisory: 21.2R3-S10 or 21.4R3-S12 or 22.4R3-S8)
#    Use the platform-specific version probe shown above.

# 2. Re-scan the host with your vulnerability scanner (Nessus, Qualys, Tenable,
#    Rapid7, OpenVAS). The scanner should no longer flag CVE-2026-21905.

# 3. Inspect service and kernel logs for crash-loops or rollback events
journalctl --since "10 minutes ago" | grep -iE 'error|fail|panic'
dmesg --since "10 minutes ago" | tail -50

If you cannot patch immediately

Front the service with rate limiting and drop malformed packets at a load balancer or IPS. Patch to remove the underlying crash condition.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for repeated service restarts, crash logs from the affected daemon, and core files generated around the time of any anomalous traffic. A memory-corruption flaw used for exploitation often leaves a trail of failed attempts before the successful one.

Frequently asked questions

Is CVE-2026-21905 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-21905?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for Junos OS run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*