Junos OS (SRX firewalls)

CVE-2025-30659: SRX Series: A device configured for vector routing crashes when receiving malformed traffic

An Improper Handling of Length Parameter Inconsistency vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on SRX Series allows an unauthenticated, network-based attacker to cause a Denial-of-Service (DoS).

Published

ExploitedNot in CISA KEV
Ransomware useNot reportedPer CISA
SeverityHIGHCVSS 4.0 8.7
EPSS0.42%Chance of exploitation in 30 days
Public exploitNot tracked
FixAvailable

Automatic summary from the vendor's CVE record. We haven't written a full analysis of this vulnerability yet.

Affected and fixed versions

Product / branchFixed in
Junos OS (SRX Series) 21.4R121.4* or later
Junos OS (SRX Series) 22.222.2R3-S6 or later
Junos OS (SRX Series) 22.422.4R3-S6 or later
Junos OS (SRX Series) 23.223.2R2-S3 or later
Junos OS (SRX Series) 23.423.4R2-S4 or later
Junos OS (SRX Series) 24.224.2R2 or later

Always confirm against the vendor advisory, which lists every fixed hotfix.

What it is

An Improper Handling of Length Parameter Inconsistency vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on SRX Series allows an unauthenticated, network-based attacker to cause a Denial-of-Service (DoS).

When a device configured for Secure Vector Routing (SVR) receives a specifically malformed packet the PFE will crash and restart. This issue affects Junos OS on SRX Series:

  • All 21.4 versions,
  • 22.2 versions before 22.2R3-S6,
  • 22.4 versions before 22.4R3-S6,
  • 23.2 versions before 23.2R2-S3,
  • 23.4 versions before 23.4R2-S4,
  • 24.2 versions before 24.2R2.

This issue does not affect versions before 21.4.

Am I affected?

To be exposed to this issue the SRX needs to be configured for SVR:

[ services vector-routing ]

Workarounds

There are no known workarounds for this issue.

Exploitation

Juniper SIRT is not aware of any malicious exploitation of this vulnerability.

Sources

KEV status, EPSS score and vendor data refreshed automatically, last on 13 Oct 2026.

Get alerts

A notification when we publish a new analysis or a covered vendor gets a new actively exploited CVE. No account, no email.