# CVE-2026-33785: Junos OS: MX Series: Missing Authorization for specific 'request' CLI commands in a JDM/CSDS scenario

> Low-privileged users can execute restricted CLI commands in specific JDM/CSDS scenarios, leading to complete device compromise.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:H/SI:H/SA:H/AU:Y/R:U/RE:M`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Apr 2026
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-m5fr-cwvv-7qff

## What is CVE-2026-33785?

CVE-2026-33785 is a medium-severity missing authorization vulnerability in Juniper Junos, published on 9 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-33785?

It affects 1 product.


Products: Juniper Junos.

## How do I fix CVE-2026-33785?

No fix has been published for CVE-2026-33785 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-33785 being exploited?

There is no known exploitation of CVE-2026-33785 in the wild and no public exploit code.

## Other vulnerabilities in Juniper Junos

- [CVE-2023-36845](https://insights.sbomify.com/CVE-2023-36845/): Juniper Junos OS EX Series and SRX Series PHP External Variable Modification (critical 9.8, exploited in the wild)
- [CVE-2020-1631](https://insights.sbomify.com/CVE-2020-1631/): Juniper Junos OS Path Traversal (high 8.8, exploited in the wild)
- [CVE-2025-21590](https://insights.sbomify.com/CVE-2025-21590/): Juniper Junos OS Improper Isolation or Compartmentalization (medium 6.7, exploited in the wild)
- [CVE-2023-36851](https://insights.sbomify.com/CVE-2023-36851/): Juniper Junos OS SRX Series Missing Authentication for Critical Function (medium 5.3, exploited in the wild)
- [CVE-2023-36844](https://insights.sbomify.com/CVE-2023-36844/): Juniper Junos OS EX Series PHP External Variable Modification (medium 5.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33785 and fix it if it is affected.

What it is: CVE-2026-33785 is a medium-severity missing authorization vulnerability in Juniper Junos, published on 9 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33785 in the wild and no public exploit code.

Affected product: Juniper Junos. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33785/ (Markdown: https://insights.sbomify.com/CVE-2026-33785/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33785
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33785
- OSV: https://osv.dev/vulnerability/CVE-2026-33785

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33785/
Summaries are generated and may contain mistakes; the official description above is the record.