# CVE-2025-59967: Null dereference in Junos OS Evolved

> An unauthenticated adjacent attacker can cause a denial of service by sending specific multicast traffic to vulnerable Juniper ACX routers.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/AU:Y/R:A/V:C/RE:M/U:Green`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2025
- **Updated:** 9 Oct 2025
- **Also known as:** GHSA-v9vh-vj86-fh3j

## What is CVE-2025-59967?

CVE-2025-59967 is a high-severity vulnerability in Juniper Junos Os Evolved, published on 9 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2025-59967?

It affects 1 product.


Products: Juniper Junos Os Evolved.

## How do I fix CVE-2025-59967?

No fix has been published for CVE-2025-59967 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-59967 being exploited?

There is no known exploitation of CVE-2025-59967 in the wild and no public exploit code.

## Other vulnerabilities in Juniper Junos Os Evolved

- [CVE-2026-21902](https://insights.sbomify.com/CVE-2026-21902/): Junos OS Evolved: PTX Series: A vulnerability allows a unauthenticated, network-based attacker to execute code as root (critical 9.3)
- [CVE-2023-28983](https://insights.sbomify.com/CVE-2023-28983/): Junos OS Evolved: Shell Injection vulnerability in the gNOI server (high 8.8)
- [CVE-2025-21599](https://insights.sbomify.com/CVE-2025-21599/): Denial of service in Junos OS Evolved (high 8.7)
- [CVE-2024-47502](https://insights.sbomify.com/CVE-2024-47502/): Junos OS Evolved: TCP session state is not always cleared on the Routing Engine leading to DoS (high 8.7)
- [CVE-2024-39531](https://insights.sbomify.com/CVE-2024-39531/): Junos OS Evolved: ACX 7000 Series: Protocol specific DDoS configuration affects other protocols (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59967 and fix it if it is affected.

What it is: CVE-2025-59967 is a high-severity vulnerability in Juniper Junos Os Evolved, published on 9 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59967 in the wild and no public exploit code.

Affected product: Juniper Junos Os Evolved. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-59967/ (Markdown: https://insights.sbomify.com/CVE-2025-59967/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59967
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59967
- OSV: https://osv.dev/vulnerability/CVE-2025-59967

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59967/
Summaries are generated and may contain mistakes; the official description above is the record.