PFE crash via corrupted unilist ECMP state
Published Jul 9, 2026 · Updated Jul 9, 2026
Improper exceptional-condition handling in Junos OS Evolved on PTX Series allows remote attackers to crash the PFE via routing updates. In 24.4R2-EVO before 24.4R2-S3-EVO and 25.2 before 25.2R2-EVO, evo-aftmand corrupts internal state while processing continuous updates that produce unified-list ECMP routes. Exploitation requires an event sequence outside the attacker’s direct control, and recovery requires an FPC restart or system reboot.
Summary
What happened
Improper exceptional-condition handling in Junos OS Evolved on PTX Series allows remote attackers to crash the PFE via routing updates. In 24.4R2-EVO before 24.4R2-S3-EVO and 25.2 before 25.2R2-EVO, evo-aftmand corrupts internal state while processing continuous updates that produce unified-list ECMP routes. Exploitation requires an event sequence outside the attacker’s direct control, and recovery requires an FPC restart or system reboot.
The record
- CVE
- CVE-2026-33794
- Published
- Jul 9, 2026
- Updated
- Jul 9, 2026
- Vendor
- Juniper Networks
- Product
- Junos OS Evolved
- Classifications
- CWE-754, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 9, 2026CVE publishedPublication date reported by the CVE source.
- Jul 9, 2026Record 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=24.4R2-EVO <24.4R2-S3-EVO
- Affected versionversion=25.2 <25.2R2, 25.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