dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2025-59967

MEDIUM · 6.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 →
70/100
Remediation priority · Elevated
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 NULL Pointer Dereference vulnerability in the PFE management daemon (evo-pfemand) of Juniper Networks Junos OS Evolved on ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7348, ACX7509 devices allows an unauthenticated, adjacent attacker to cause a Denial-of-Service (DoS). Whenever specific valid multicast traffic is received on any layer 3 interface the evo-pfemand process crashes and restarts. Continued receipt of specific valid multicast traffic results in a sustained Denial of Service (DoS) attack. This issue affects Junos OS Evolved on ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7348, ACX7509:  * from 23.2R2-EVO before 23.2R2-S4-EVO,  * from 23.4R1-EVO before 23.4R2-EVO. This issue affects IPv4 and IPv6. This issue does not affect Junos OS Evolved ACX7024, ACX7024X, ACX7100-32C, ACX7100-48L, ACX7348, ACX7509 versions before 23.2R2-EVO.

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 NULL pointer dereference vulnerability in the PFE management daemon (evo-pfemand) in Juniper Networks Junos OS Evolved allows an unauthenticated adjacent attacker to cause denial of service by sending specific valid multicast traffic on any layer 3 interface, which triggers a process crash and restart.

MitigationUpgrade Junos OS Evolved to version 23.2R2-S4-EVO or later, or 23.4R2-EVO or later. As a temporary workaround, consider filtering the specific trigger multicast traffic at layer 3 boundaries if identifiable.

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
Junos Os EvolvedOperating system
Affected:= 23.2= 23.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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/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. Confirm device runs Junos OS Evolved
    Execute 'show version' and look for 'Junos OS Evolved' in the output, not just 'Junos OS'. This CVE only affects the Evolved variant.
    Affected if Device is NOT running Junos OS Evolved (running plain Junos OS instead)
  2. Identify installed Junos OS Evolved version
    Run 'show version' and locate the version string (e.g., 23.2R1, 23.4R1, etc.). Compare against affected versions 23.2 and 23.4.
    Affected if Version is exactly 23.2 or 23.4 (any sub-version like 23.2R1, 23.4R1-S1, etc.)
  3. Verify layer 3 interfaces are configured
    Run 'show interfaces terse' and check for layer 3 interfaces (inet addresses) on any interface. The vulnerability triggers when valid multicast traffic is sent on any L3 interface.
    Affected if No layer 3 interfaces are configured or active on the device

Device is affected if it runs Junos OS Evolved versions 23.2 or 23.4 AND has at least one active layer 3 interface that can receive the trigger multicast traffic.

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

Upgrade Junos OS Evolved to version 23.2R2-S4-EVO or later, or 23.4R2-EVO or later. As a temporary workaround, consider filtering the specific trigger multicast traffic at layer 3 boundaries if identifiable.

Recommended fix High confidence

23.2R2-S4-EVO or later for 23.2 branch; 23.4R2-EVO or later for 23.4 branch

  1. 1. Identify the current Junos OS Evolved version on the affected device using 'show version' command.
  2. 2. Determine which branch (23.2 or 23.4) your device is currently running.
  3. 3. For devices on 23.2 branch: Upgrade to Junos OS Evolved 23.2R2-S4-EVO or later.
  4. 4. For devices on 23.4 branch: Upgrade to Junos OS Evolved 23.4R2-EVO or later.
  5. 5. Download the appropriate software image from the Juniper Networks support portal (supportportal.juniper.net).
  6. 6. Transfer the software image to the device using 'file copy' or USB media.
  7. 7. Install the software using 'request system software add <package-name> reboot' command.
  8. 8. After reboot, verify the new version is installed using 'show version'.
Caveat Standard Junos upgrade considerations apply - review release notes for any migration steps or compatibility notices before upgrading

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

Fix this in Junos Os Evolved Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59967 — 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-59967 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