dbcve.org
JunosOperating system · Juniper

CVE-2025-59964

HIGH · 7.5 CVSS v3.1 Published 2025-10-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A Use of Uninitialized Resource vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on SRX4700 devices allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). When forwarding-options sampling is enabled, receipt of any traffic destined to the Routing Engine (RE) by the PFE line card leads to an FPC crash and restart, resulting in a Denial of Service (DoS). Continued receipt and processing of any traffic leading to the RE by the PFE line card will create a sustained Denial of Service (DoS) condition to the PFE line card. This issue affects Junos OS on SRX4700:  * from 24.4 before 24.4R1-S3, 24.4R2 This issue affects IPv4 and IPv6.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A Use of Uninitialized Resource vulnerability in the Packet Forwarding Engine (PFE) of Juniper Junos OS on SRX4700 devices causes an FPC crash and restart when forwarding-options sampling is enabled and traffic destined to the Routing Engine is received, resulting in a reproducible DoS condition.

MitigationDisable forwarding-options sampling on affected SRX4700 devices or upgrade to Junos OS 24.4R1-S3, 24.4R2 or later versions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JunosOperating system
Affected:= 24.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Run 'show chassis hardware' or 'show system information' to confirm the device is an SRX4700
    Affected if Device model is not SRX4700 - not affected by this specific vulnerability
  2. Check Junos OS version
    Run 'show version' to identify the installed Junos OS version
    Affected if Version is exactly 24.4 (or a build within 24.4) - falls within affected version range
  3. Verify forwarding-options sampling configuration
    Run 'show configuration forwarding-options sampling' to check if sampling is enabled
    Affected if Output shows sampling is configured and active - condition required for exploit
  4. Confirm FPC process status
    Run 'show chassis fpc status' to verify FPC operational state
    Affected if FPC shows crash/restart patterns or instability - may indicate active exploitation

Device is affected only if it is an SRX4700 running Junos OS 24.4 with forwarding-options sampling currently enabled in the configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable forwarding-options sampling on affected SRX4700 devices or upgrade to Junos OS 24.4R1-S3, 24.4R2 or later versions.

Recommended fix High confidence

24.4R1-S3 or later (24.4R2 or latest stable 24.4 release)

  1. 1. Identify the current Junos OS version on the affected SRX4700 device using 'show version'
  2. 2. Confirm forwarding-options sampling is enabled using 'show configuration forwarding-options sampling'
  3. 3. Schedule a maintenance window as the fix requires a system upgrade
  4. 4. Download Junos OS 24.4R1-S3 or later from the Juniper support portal
  5. 5. Upload the upgrade package to the SRX4700 device
  6. 6. Install the upgrade using 'request system software add <package-name> reboot'
  7. 7. After reboot, verify the new version is installed with 'show version'
  8. 8. Confirm the device is functioning normally and forwarding traffic
Caveat Standard Junos upgrade precautions apply - verify hardware compatibility, backup configuration, and plan for brief downtime during reboot

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59964 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59964 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data