Resource exhaustion and disclosure via rejected packets
Published Oct 9, 2025 · Updated Oct 9, 2025
Improper condition handling in Junos OS Evolved allows remote attackers to disrupt service and read device data through rejected packets. The PFE incorrectly forwards packets matching an output-filter reject term to the Routing Engine for further processing instead of rejecting them. The issue affects all versions before 22.4R3-EVO and 23.2 before 23.2R2-EVO only when the output filter is applied to a WAN or revenue interface.
Summary
What happened
Improper condition handling in Junos OS Evolved allows remote attackers to disrupt service and read device data through rejected packets. The PFE incorrectly forwards packets matching an output-filter reject term to the Routing Engine for further processing instead of rejecting them. The issue affects all versions before 22.4R3-EVO and 23.2 before 23.2R2-EVO only when the output filter is applied to a WAN or revenue interface.
The record
- CVE
- CVE-2025-59958
- Published
- Oct 9, 2025
- Updated
- Oct 9, 2025
- Vendor
- Juniper Networks
- Product
- Junos OS Evolved
- Classifications
- CWE-754, T1498.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 9, 2025CVE publishedPublication date reported by the CVE source.
- Oct 9, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <22.4R3-EVO
- Affected versionversion=23.2 <23.2R2-EVO
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo