Skip to content
major vulnerability· requires attention

Widely deployed Juniper SRX firewalls; DoS could disrupt network perimeter across many organizations.

Networks

CVE-2026-33790

8.7
High
EPSS 0.33%Patch availableApr 10, 2026

DoS in Junos SRX flowd via malformed ICMPv6 packet.

common questions

Is CVE-2026-33790 being exploited?

Not confirmed. CVE-2026-33790 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.33% probability of exploitation in the next 30 days.

How severe is CVE-2026-33790?

CVE-2026-33790 is rated High with a CVSS score of 8.7. 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-33790?

Yes. A fix has been recorded for CVE-2026-33790. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-33790 affect?

CVE-2026-33790 affects Juniper Networks Junos OS (SRX Series). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-33790?

Plan upgrade to fixed Junos SRX releases when available

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Juniper Networks Junos OS (SRX Series)
impact

ICMPv6-based DoS crashes srxpfe, rebooting SRX devices and disrupting firewall services.

action required

Monitor only

affected versions
Juniper Networks Junos OS
  • affected< 21.2R3-S10
  • affected>= 21.4 and < 21.4R3-S12
  • affected>= 22.2 and < 22.2R3-S8
  • affected>= 22.4 and < 22.4R3-S9
  • affected>= 23.2 and < 23.2R2-S6
  • affected>= 23.4 and < 23.4R2-S7
  • affected>= 24.2 and < 24.2R2-S3
  • affected>= 24.4 and < 24.4R2-S3
  • affected>= 25.2 and < 25.2R1-S2, 25.2R2
  • affected>= 21.3 and < 21.3*
  • affected>= 22.1 and < 22.1*
  • affected>= 22.3 and < 22.3*

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free