CVE-2026-33790: Junos OS: SRX Series: In a NAT64 configuration, receipt of a specific, malformed ICMPv6 packet will cause the srxpfe process to crash and restart.
An Improper Check for Unusual or Exceptional Conditions vulnerability in the flow daemon (flowd) of Juniper Networks Junos OS on SRX Series allows an attacker sending a specific, malformed ICMPv6 packet to cause the srxpfe process to crash and restart. Continued receipt and processing of these packets will repeatedly crash the srxpfe process and sustain the Denial of Service (DoS) condition.
During NAT64 translation, receipt of a specific, malformed ICMPv6 packet destined to the device will cause the srxpfe process to crash and restart.
This issue cannot be triggered using IPv4 nor other IPv6 traffic.
This issue affects Junos OS on SRX Series: all versions before 21.2R3-S10, all versions of 21.3, from 21.4 before 21.4R3-S12, all versions of 22.1, from 22.2 before 22.2R3-S8, all versions of 22.4, from 22.4 before 22.4R3-S9, from 23.2 before 23.2R2-S6, from 23.4 before 23.4R2-S7, from 24.2 before 24.2R2-S3, from 24.4 before 24.4R2-S3, from 25.2 before 25.2R1-S2, 25.2R2.
Affected Software
Remediation
Information
Event History
Frequently Asked Questions
What is the severity of CVE-2026-33790?
CVE-2026-33790 has been assigned a severity rating indicating that it poses a significant risk to systems running affected versions of Junos OS on SRX Series.
How do I fix CVE-2026-33790?
To fix CVE-2026-33790, upgrade to a fixed version of Junos OS as specified in Juniper Networks' security advisories.
What types of devices are impacted by CVE-2026-33790?
CVE-2026-33790 affects various models of Juniper Networks SRX Series devices running specific versions of Junos OS.
What are the symptoms of an exploitation of CVE-2026-33790?
Exploitation of CVE-2026-33790 may lead to the crashing and restarting of the srxpfe process within the affected systems.
Is CVE-2026-33790 being actively exploited in the wild?
There is currently no public indication that CVE-2026-33790 is being actively exploited, but it remains a critical vulnerability.