dbcve.org
JunosOperating system · Juniper

CVE-2026-33793

HIGH · 7.8 CVSS v3.1 Published 2026-04-09
Fix available
A fix is available. Upgrade to 22.4 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An Execution with Unnecessary Privileges vulnerability in the User Interface (UI) of Juniper Networks Junos OS and Junos OS Evolved allows a local, low-privileged attacker to gain root privileges, thus compromising the system. When a configuration that allows unsigned Python op scripts is present on the device, a non-root user is able to execute malicious op scripts as a root-equivalent user, leading to privilege escalation.  This issue affects Junos OS:  * All versions before 22.4R3-S7,  * from 23.2 before 23.2R2-S4,  * from 23.4 before 23.4R2-S6, * from 24.2 before 24.2R1-S2, 24.2R2,  * from 24.4 before 24.4R1-S2, 24.4R2;  Junos OS Evolved:  * All versions before 22.4R3-S7-EVO,  * from 23.2 before 23.2R2-S4-EVO,  * from 23.4 before 23.4R2-S6-EVO, * from 24.2 before 24.2R2-EVO,  * from 24.4 before 24.4R1-S1-EVO, 24.4R2-EVO.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A local low-privileged attacker with access to a Junos OS or Junos OS Evolved device configured to allow unsigned Python op scripts can execute malicious scripts as root-equivalent user through the UI, achieving full privilege escalation and system compromise.

MitigationUpgrade to the patched versions specified in the Juniper advisory (22.4R3-S7, 23.2R2-S4, 23.4R2-S6, 24.2R2, 24.4R2 or later). As an interim workaround, disable unsigned Python op scripts in the device configuration if not required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JunosOperating system
Affected:< 22.4= 22.4= 23.2= 23.4= 24.2= 24.4
Junos Os EvolvedOperating system
Affected:< 22.4= 22.4= 23.2= 23.4= 24.2= 24.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Junos OS version
    Run 'show version' or 'show version detail' on the device CLI to obtain the installed software version.
    Affected if The installed version is < 22.4, = 22.4, = 23.2, = 23.4, = 24.2, or = 24.4 (or any version not listed as fixed: 22.4R3-S7, 23.2R2-S4, 23.4R2-S6, 24.2R2, 24.4R2 or later).
  2. Verify if op scripts are configured
    Run 'show configuration system scripts' to see if op scripts are enabled in the configuration.
    Affected if The 'op' or 'python' script configuration exists under system scripts.
  3. Check unsigned Python op scripts permission
    Run 'show configuration system scripts op' and look for 'allow-unverified-python' or 'unsigned-python' setting, or inspect the full config with 'show configuration | display set | match unsigned' to see if unsigned Python op scripts are permitted.
    Affected if The configuration contains 'allow-unverified-python' or 'unsigned-python' or similar setting that permits unsigned Python op scripts to run.

The device is affected if it runs a vulnerable Junos version AND has unsigned Python op scripts enabled in the configuration, allowing a low-privileged user to execute arbitrary Python code as root.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 22.4 or later
Fixed in 22.4
Interim mitigation

Upgrade to the patched versions specified in the Juniper advisory (22.4R3-S7, 23.2R2-S4, 23.4R2-S6, 24.2R2, 24.4R2 or later). As an interim workaround, disable unsigned Python op scripts in the device configuration if not required.

Recommended fix High confidence

Upgrade to one of: Junos OS 22.4R3-S7, 23.2R2-S4, 23.4R2-S6, 24.2R2, 24.4R2 (or later); Junos OS Evolved 22.4R3-S7-EVO, 23.2R2-S4-EVO, 23.4R2-S6-EVO, 24.2R2-EVO, 24.4R2-EVO (or later)

  1. 1. Identify the current Junos OS or Junos OS Evolved version running on the device using 'show version'
  2. 2. Determine the appropriate fixed release based on your current branch (22.4, 23.2, 23.4, 24.2, or 24.4)
  3. 3. Schedule a maintenance window for the upgrade
  4. 4. Back up the current configuration using 'request system configuration rescue save'
  5. 5. Download the appropriate Junos OS or Junos OS Evolved software from the Juniper Networks support portal
  6. 6. Copy the software package to the device using 'file copy' or USB
  7. 7. Install the software using 'request system software add <package-name> reboot'
  8. 8. After reboot, verify the new version using 'show version'
Caveat Standard Junos upgrade risks apply - test in lab first, ensure configuration compatibility, and plan for potential rollback if issues occur

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33793 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33793 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data