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.

HIGH

7.5

CVSS Score

Published: April 9, 2026 at 09:38 PM UTC

Updated: June 17, 2026 at 10:38 AM UTC

1 product affected across 1 vendorJunos

Using Junos OS by Juniper Networks?

Get instant alerts when new vulnerabilities affect Junos OS - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.5

Exploit prediction

EPSS 0.3%

SSVC

No known exploit

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Junos · Juniper Networks

95%

v < 21.2v < 21.2R3-S1021.3 ≤ v < 21.3*21.4 ≤ v < 21.4R3-S1222.1 ≤ v < 22.1*22.2 ≤ v < 22.2R3-S822.3 ≤ v < 22.3*22.4 ≤ v < 22.4R3-S923.2 ≤ v < 23.2R2-S623.4 ≤ v < 23.4R2-S724.2 ≤ v < 24.2R2-S324.4 ≤ v < 24.4R2-S325.2 ≤ v < 25.2R1-S2, 25.2R221.2 21.2 r1 21.2 r1-s1 21.2 r1-s2 21.2 r2 21.2 r2-s1 21.2 r2-s2 21.2 r3 21.2 r3-s1 21.2 r3-s2 21.2 r3-s3 21.2 r3-s4 21.2 r3-s5 21.2 r3-s6 21.2 r3-s7 21.2 r3-s8 21.2 r3-s9 21.3 21.4 21.4 r1 21.4 r1-s1 21.4 r1-s2 21.4 r2 21.4 r2-s1 21.4 r2-s2 21.4 r3 21.4 r3-s1 21.4 r3-s10 21.4 r3-s11 21.4 r3-s2 21.4 r3-s3 21.4 r3-s4 21.4 r3-s5 21.4 r3-s6 21.4 r3-s7 21.4 r3-s8 21.4 r3-s9 22.1 22.2 22.2 r1 22.2 r1-s1 22.2 r1-s2 22.2 r2 22.2 r2-s1 22.2 r2-s2 22.2 r3 22.2 r3-s1 22.2 r3-s2 22.2 r3-s3 22.2 r3-s4 22.2 r3-s5 22.2 r3-s6 22.2 r3-s7 22.3 22.4 22.4 r1 22.4 r1-s1 22.4 r1-s2 22.4 r2 22.4 r2-s1 22.4 r2-s2 22.4 r3 22.4 r3-s1 22.4 r3-s2 22.4 r3-s3 22.4 r3-s4 22.4 r3-s5 22.4 r3-s6 22.4 r3-s7 22.4 r3-s8 23.2 23.2 r1 23.2 r1-s1 23.2 r1-s2 23.2 r2 23.2 r2-s1 23.2 r2-s2 23.2 r2-s3 23.2 r2-s4 23.2 r2-s5 23.4 23.4 r1 23.4 r1-s1 23.4 r1-s2 23.4 r2 23.4 r2-s1 23.4 r2-s2 23.4 r2-s3 23.4 r2-s4 23.4 r2-s5 23.4 r2-s6 24.2 24.2 r1 24.2 r1-s1 24.2 r1-s2 24.2 r2 24.2 r2-s1 24.2 r2-s2 24.4 24.4 r1 24.4 r1-s2 24.4 r1-s3 24.4 r2 24.4 r2-s1 24.4 r2-s2 25.2 25.2 r1 25.2 r1-s1 25.2 r2

Affected range stops below 21.2R3-S10, so it looks safe — our inference, not a vendor statement

Affected range stops below 21.3*, so it looks safe — our inference, not a vendor statement

Affected range stops below 21.4R3-S12, so it looks safe — our inference, not a vendor statement

Affected range stops below 22.1*, so it looks safe — our inference, not a vendor statement

Affected range stops below 22.2R3-S8, so it looks safe — our inference, not a vendor statement

Affected range stops below 22.3*, so it looks safe — our inference, not a vendor statement

Affected range stops below 22.4R3-S9, so it looks safe — our inference, not a vendor statement

Affected range stops below 23.2R2-S6, so it looks safe — our inference, not a vendor statement

Affected range stops below 23.4R2-S7, so it looks safe — our inference, not a vendor statement

Affected range stops below 24.2R2-S3, so it looks safe — our inference, not a vendor statement

Affected range stops below 24.4R2-S3, so it looks safe — our inference, not a vendor statement

Affected range stops below 25.2R1-S2, 25.2R2, so it looks safe — our inference, not a vendor statement

juniper-srx1500 (environment) · juniper-srx1600 (environment) · juniper-srx2300 (environment) · juniper-srx300 (environment) · juniper-srx320 (environment) · juniper-srx340 (environment) · juniper-srx345 (environment) · juniper-srx380 (environment) · juniper-srx4100 (environment) · juniper-srx4120 (environment) · juniper-srx4200 (environment) · juniper-srx4300 (environment) · juniper-srx4600 (environment) · juniper-srx4700 (environment) · juniper-srx5400 (environment) · juniper-srx5600 (environment) · juniper-srx5800 (environment)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://kb.juniper.net/JSA107874

References (1)

Vendor Advisory

Source: cverecord

https://kb.juniper.net/JSA107874

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHjuniper

Attack Vector: NETWORK
Complexity: LOW
Privileges: NONE
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: NONE
Integrity: NONE
Availability: HIGH

Vector?

Quick Info

StatusANALYZED

CWE

CWE-754

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card