Affects widely deployed Juniper MX/SRX routing/firewall platforms; can cause device-wide DoS disrupting network infrastructure across industries.
CVE-2026-57022
Unauthenticated network-triggered PFE crash in Juniper MX/SRX causing device DoS.
Is CVE-2026-57022 being exploited?
Not confirmed. CVE-2026-57022 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.40% probability of exploitation in the next 30 days.
How severe is CVE-2026-57022?
CVE-2026-57022 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-57022?
Yes. A fix has been recorded for CVE-2026-57022. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-57022 affect?
CVE-2026-57022 affects Junos OS on MX Series (SPC3), SRX5k (SPC3), SRX1600, SRX2300, and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-57022?
Upgrade to vendor-fixed releases; block outbound TCP to untrusted hosts; monitor PFE restarts.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote attacker can trigger a PFE crash by responding to an outbound TCP connection, causing device-wide DoS until restart.
Immediate action required
- affected< 23.2R2-S4
- affected>= 23.4 and < 23.4R2-S5
- affected>= 24.2 and < 24.2R2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.