CVE-2026-33794 junos os evolved vulnerability
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.
Quick answer
juniper junos os evolved should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- 24.4
- 25.2
- -
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
Juniper Junos OS Evolved is affected by CVE-2026-33794, a security exposure. 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 recommended remediation is to update to Junos OS Evolved 24.4R2-S3-EVO or 25.2R2 / 25.2R2-EVO according to the deployed branch. Until the update is complete, limit routing update exposure on affected PTX/Junos OS Evolved systems and monitor evo-aftmand stability, review logs, and reduce exposure of the affected service or workflow.
- Inventory every deployment, package, appliance, container, service, and managed environment that uses Juniper Junos OS Evolved.
- Confirm the installed version and compare it with listed affected versions include 24.4, 25.2, - and the source advisory for CVE-2026-33794.
- Apply the vendor-supported fix: update to Junos OS Evolved 24.4R2-S3-EVO or 25.2R2 / 25.2R2-EVO according to the deployed branch.
- If the update cannot be applied immediately, limit routing update exposure on affected PTX/Junos OS Evolved systems and monitor evo-aftmand stability; disable unnecessary public access, endpoints, plugins, integrations, or management interfaces until patched.
- Review application, device, reverse-proxy, WAF, package manager, container, authentication, and audit logs for activity related to CVE-2026-33794.
- Rotate sessions, API tokens, service credentials, integration keys, and administrator passwords if logs or affected data indicate compromise or unauthorized access.
- Clear caches, restart affected services, rebuild affected containers or appliances when appropriate, and remove temporary files or stored payloads created during exploitation attempts.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm Juniper Junos OS Evolved now reports Junos OS Evolved 24.4R2-S3-EVO or 25.2R2 / 25.2R2-EVO according to the deployed branch or a later vendor-supported fixed release for the deployed branch.
- Verify the affected workflow no longer allows the behavior described in CVE-2026-33794, using a safe regression test or vendor-provided validation method.
- Review logs after remediation for continued exploit attempts, denial-of-service symptoms, suspicious redirects, unauthorized requests, file access, or configuration changes.
- Rerun a Fixnx scan and any product-specific scanner, package audit, device health check, or manual regression test relevant to the affected service.
- Document affected assets, fixed versions, mitigation decisions, validation evidence, and any cleanup or credential rotation performed.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-33794?
juniper junos os evolved versions listed as affected should be reviewed: 24.4, 25.2, -.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.