Affects widely used Juniper network OS; could disrupt enterprise networks and services.
CVE-2026-33791
Junos OS/EO CLI input allows local root command injection.
Is CVE-2026-33791 being exploited?
Not confirmed. CVE-2026-33791 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.69% probability of exploitation in the next 30 days.
How severe is CVE-2026-33791?
CVE-2026-33791 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-33791?
Yes. A fix has been recorded for CVE-2026-33791. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-33791 affect?
CVE-2026-33791 affects Juniper Networks Junos OS, Juniper Networks Junos OS Evolved. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-33791?
Patch when released; restrict CLI access; monitor for anomalous CLI activity.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker can inject shell commands via crafted CLI input, gaining root and full device control.
Immediate action required
- affected< 22.4R3-S8
- affected>= 23.2 and < 23.2R2-S5
- affected>= 23.4 and < 23.4R2-S7
- affected>= 24.2 and < 24.2R2-S2
- affected>= 24.4 and < 24.4R2
- affected>= 25.2 and < 25.2R2
- affected< 22.4R3-S8-EVO
- affected>= 23.2 and < 23.2R2-S5-EVO
- affected>= 23.4 and < 23.4R2-S7-EVO
- affected>= 24.2 and < 24.2R2-S2-EVO
- affected>= 24.4 and < 24.4R2-EVO
- affected>= 25.2 and < 25.2R1-S1-EVO, 25.2R2-EVO
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.