# CVE-2025-59958: Junos OS Evolved: PTX Series: When a firewall filter rejects traffic these packets are erroneously sent to the RE

> An attacker can cause rejected packets to reach the Routing Engine, leading to resource exhaustion and potential information disclosure on Juniper PTX routers.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N/RE:M`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2025
- **Updated:** 9 Oct 2025
- **Also known as:** GHSA-v4g8-gwfh-3cj3

## What is CVE-2025-59958?

CVE-2025-59958 is a medium-severity vulnerability in Juniper Junos Os Evolved, published on 9 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Improper Check for Unusual or Exceptional Conditions vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS Evolved on PTX Series allows an unauthenticated, network-based attacker to cause impact to confidentiality and availability.

When an output firewall filter is configured with one or more terms where the action is 'reject', packets matching these terms are erroneously sent to the Routing Engine (RE) and further processed there. Processing of these packets will consume limited RE resources. Also responses from the RE back to the source of this traffic could reveal confidential information about the affected device.
This issue only applies to firewall filters applied to WAN or revenue interfaces, so not the mgmt or lo0 interface of the routing-engine, nor any input filters.

This issue affects Junos OS Evolved on PTX Series:

  *  all versions before 22.4R3-EVO,
  *  23.2 versions before 23.2R2-EVO.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

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

It affects 1 product.


Products: Juniper Junos Os Evolved.

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

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

## Is CVE-2025-59958 being exploited?

There is no known exploitation of CVE-2025-59958 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-59958 and fix it if it is affected.

What it is: CVE-2025-59958 is a medium-severity vulnerability in Juniper Junos Os Evolved, published on 9 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59958 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-59958/ (Markdown: https://insights.sbomify.com/CVE-2025-59958/index.md)
```

## Sources

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

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