# CVE-2026-33776: Junos OS and Junos OS Evolved: Specific low privileged CLI command exposes sensitive information

> A local low-privileged user can execute a specific CLI command to expose sensitive information due to missing authorization checks.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/AU:Y/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:** 10 Apr 2026
- **Also known as:** GHSA-cp8x-pvqx-wpcc

## What is CVE-2026-33776?

CVE-2026-33776 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 and Junos OS Evolved allows a local user with low privileges to read sensitive information.

A local user with low privileges can execute the CLI command 'show mgd' with specific arguments which will expose sensitive information.

This issue affects

Junos OS:
  *  all versions before 22.4R3-S8,
  *  23.2 versions before 23.2R2-S6,
  *  23.4 versions before 23.4R2-S6,
  *  24.2 versions before 24.2R2-S4,
  *  24.4 versions before 24.4R2-S1,
  *  25.2 version before 25.2R1-S2, 25.2R2;

Junos OS Evolved:
  *  all versions before 23.2R2-S6-EVO,
  *  23.4 version before 23.4R2-S6-EVO,
  *  24.2 version before 24.2R2-S4-EVO,
  *  24.4 versions before 24.4R2-S1-EVO,
  *  25.2 versions before 25.2R2-EVO.

Weakness: CWE-862 (Missing Authorization)

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

It affects 2 products.


Products: Juniper Junos, Juniper Junos Os Evolved.

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

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

## Is CVE-2026-33776 being exploited?

There is no known exploitation of CVE-2026-33776 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-33776 and fix it if it is affected.

What it is: CVE-2026-33776 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-33776 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-33776/ (Markdown: https://insights.sbomify.com/CVE-2026-33776/index.md)
```

## Sources

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

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