dbcve.org
JunosOperating system · Juniper

CVE-2026-33785

HIGH · 8.8 CVSS v3.1 Published 2026-04-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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
A Missing Authorization vulnerability in the CLI of Juniper Networks Junos OS on MX Series allows a local, authenticated user with low privileges to execute specific commands which will lead to a complete compromise of managed devices. Any user logged in, without requiring specific privileges, can issue 'request csds' CLI operational commands. These commands are only meant to be executed by high privileged or users designated for Juniper Device Manager (JDM) / Connected Security Distributed Services (CSDS) operations as they will impact all aspects of the devices managed via the respective MX. This issue affects Junos OS on MX Series: * 24.4 releases before 24.4R2-S3,  * 25.2 releases before 25.2R2. This issue does not affect Junos OS releases before 24.4.

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 Missing Authorization vulnerability in the Juniper Junos OS CLI on MX Series allows any authenticated user with low privileges to execute 'request csds' operational commands that should be restricted to high-privileged users or designated JDM/CSDS administrators, potentially leading to complete compromise of managed devices.

MitigationApply vendor patches: upgrade to 24.4R2-S3 or later for 24.4 releases, or 25.2R2 or later for 25.2 releases. Alternatively, restrict CLI access to trusted high-privileged users until patching is feasible.

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:= 24.4= 25.2

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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. Confirm device is MX Series
    Run 'show chassis hardware' or 'show chassis inventory' and verify the model field indicates an MX Series router
    Affected if Device is not an MX Series router - this CVE only affects MX Series devices
  2. Identify installed Junos version
    Run 'show version' and note the full Junos version string (for example, 24.4R1-S2, 24.4R2, 25.2R1)
    Affected if Version matches 24.4.x or 25.2.x (exact versions per vendor advisory)
  3. Check for low-privilege authenticated users
    Run 'show system users' to list currently logged-in users, or review 'show configuration system login' for user accounts with operator, read-only, or super-user lesser privileges
    Affected if Any authenticated user accounts with non-super-user privileges exist on the device
  4. Test request csds command access with low-privilege account
    Log in with a low-privilege account (operator/read-only class) and attempt to run 'request csds' operational commands
    Affected if The command executes successfully without authorization error - indicating the vulnerability is present

Device is affected if it is an MX Series running Junos 24.4.x or 25.2.x AND has any authenticated users with low privileges who can execute request csds commands without proper authorization checks.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches: upgrade to 24.4R2-S3 or later for 24.4 releases, or 25.2R2 or later for 25.2 releases. Alternatively, restrict CLI access to trusted high-privileged users until patching is feasible.

Recommended fix High confidence

24.4R2-S3 or later for 24.4 branch; 25.2R2 or later for 25.2 branch

  1. Identify the current Junos OS version running on the MX Series device using 'show version'
  2. If running 24.4.x: upgrade to Junos OS 24.4R2-S3 or later
  3. If running 25.2.x: upgrade to Junos OS 25.2R2 or later
  4. After upgrade, verify the fix by confirming low-privilege users can no longer execute 'request csds' commands
  5. Alternatively, restrict CLI access by implementing proper user role-based access controls (RBAC) to limit which users can execute privileged operational commands
Caveat Standard Junos OS upgrade procedures apply; test in lab environment before production deployment

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

Fix this in Junos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33785 — 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-33785 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