CVE-2026-33794

Junos OS Evolved: PTX Series: Receipt of repeated ECMP routing updates results in PFE crash

MEDIUM
5.9
CVSS Score
Published: July 9, 2026 at 09:02 PM UTC
Updated: October 25, 2026 at 05:10 PM UTC
2 products affected across 2 vendorsJunos OS EvolvedJunos OS Evolved· also runs on 18 platforms

Using Junos OS Evolved by Juniper Networks?

Get instant alerts when new vulnerabilities affect Junos OS Evolved - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.9
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

An Improper Check for Unusual or Exceptional Conditions vulnerability in the advanced forwarding toolkit (evo-aftmand) of Juniper Networks Junos OS Evolved on PTX Series allows an unauthenticated network-based attacker generating continuous routing updates, resulting in unilist ECMP routes, to crash the evo-aftmand process on the PFE, leading to a Denial-of-Service (DoS). The conditions required for successful exploitation are based on a sequence of events that are outside an attacker's direct control. Unified list (unilist) ECMP routes are a specific ECMP behavior where multiple equal-cost routes share a single logical next-hop list entry. The router treats them as one route with multiple next hops and load balances traffic across that unified list. Due to an issue processing unilist ECMP routing updates, internal state corruption may occur, especially in large-scale ECMP unilist deployments, leading to the evo-aftmand process crashing, resulting in an evo-aftmand-bx core. Manual intervention is required to recover by rebooting the system or restarting the FPC. This issue affects Junos OS Evolved on PTX : * from 24.4R2-EVO before 24.4R2-S3-EVO; * from 25.2 before 25.2R2-EVO.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

juniper-ptx1000-72q (environment) · juniper-ptx10000 (environment) · juniper-ptx10001 (environment) · juniper-ptx10001-36mr (environment) · juniper-ptx100016 (environment) · juniper-ptx10002 (environment) · juniper-ptx10002-36qdd (environment) · juniper-ptx10002-60c (environment) · juniper-ptx10003 (environment) · juniper-ptx10003-160c (environment) · juniper-ptx10003-80c (environment) · juniper-ptx10003-81cd (environment) · juniper-ptx10004 (environment) · juniper-ptx10008 (environment) · juniper-ptx10016 (environment) · juniper-ptx12008 (environment) · juniper-ptx3000 (environment) · juniper-ptx5000 (environment)
24.4R2-EVO ≤ v < 24.4R2-S3-EVO25.2 ≤ v < 25.2R2, 25.2R2-EVO24.4R2-EVO25.2
Affected range stops below 24.4R2-S3-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 25.2R2, 25.2R2-EVO, so it looks safe — our inference, not a vendor statement

Runs on — not affected

The affected product only carries this flaw when running on these platforms. The platforms themselves are not vulnerable.

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (1)

Vendor AdvisoryMitigation
Source: cverecord
https://supportportal.juniper.net/JSA110073

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.9MEDIUMjuniper
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-754

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card