# CVE-2026-33788: Junos OS Evolved: Local, authenticated attacker can gain privileged access to FPCs

> A local authenticated attacker can bypass authentication to gain privileged access to Flexible PIC Concentrators, potentially compromising the device.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:L/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:** 13 Apr 2026
- **Also known as:** GHSA-w5q7-9fqr-f6hx

## What is CVE-2026-33788?

CVE-2026-33788 is a high-severity missing authorization vulnerability in Juniper Junos Os Evolved, 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 Authentication for Critical Function vulnerability in the Flexible PIC Concentrators (FPCs) of Juniper Networks Junos OS Evolved on PTX Series allows a local, authenticated attacker with low privileges to gain direct access to FPCs installed in the device.

A local user with low privileges can gain direct access to the installed FPCs as a high privileged user, which can potentially lead to a full compromise of the affected component.

This issue affects Junos OS Evolved on PTX10004, PTX10008, PTX100016, with JNP10K-LC1201 or JNP10K-LC1202:

  *  All versions before 21.2R3-S8-EVO,
  *  21.4-EVO versions before 21.4R3-S7-EVO,
  *  22.2-EVO versions before 22.2R3-S4-EVO,
  *  22.3-EVO versions before 22.3R3-S3-EVO,
  *  22.4-EVO versions before 22.4R3-S2-EVO,
  *  23.2-EVO versions before 23.2R2-EVO.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Juniper Junos Os Evolved.

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

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

## Is CVE-2026-33788 being exploited?

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

## Other vulnerabilities in Juniper Junos Os Evolved

- [CVE-2026-21902](https://insights.sbomify.com/CVE-2026-21902/): Junos OS Evolved: PTX Series: A vulnerability allows a unauthenticated, network-based attacker to execute code as root (critical 9.3)
- [CVE-2023-28983](https://insights.sbomify.com/CVE-2023-28983/): Junos OS Evolved: Shell Injection vulnerability in the gNOI server (high 8.8)
- [CVE-2025-21599](https://insights.sbomify.com/CVE-2025-21599/): Denial of service in Junos OS Evolved (high 8.7)
- [CVE-2024-47502](https://insights.sbomify.com/CVE-2024-47502/): Junos OS Evolved: TCP session state is not always cleared on the Routing Engine leading to DoS (high 8.7)
- [CVE-2024-39531](https://insights.sbomify.com/CVE-2024-39531/): Junos OS Evolved: ACX 7000 Series: Protocol specific DDoS configuration affects other protocols (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33788 is a high-severity missing authorization vulnerability in Juniper Junos Os Evolved, 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-33788 in the wild and no public exploit code.

Affected product: Juniper Junos Os Evolved. 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-33788/ (Markdown: https://insights.sbomify.com/CVE-2026-33788/index.md)
```

## Sources

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

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