# CVE-2025-30650: Junos OS: Privileged local user can gain access to a Linux-based FPC as root

> A privileged local user can gain root access to Linux-based line cards in Junos OS due to missing authentication for critical functions.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/AU:N/R:A/V:C/RE:M/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2026
- **Updated:** 13 Apr 2026

## What is CVE-2025-30650?

CVE-2025-30650 is a high-severity missing authorization vulnerability in Juniper Junos, published on 8 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 command processing of Juniper Networks Junos OS allows a privileged local attacker to gain access to Linux-based line cards as root.

This issue affects systems running Junos OS using Linux-based line cards. Affected line cards include:
  *  MPC7, MPC8, MPC9, MPC10, MPC11
  *  LC2101, LC2103
  *  LC480, LC4800, LC9600
  *  MX304 (built-in FPC)
  *  MX-SPC3
  *  SRX5K-SPC3
  *  EX9200-40XS

  *  FPC3-PTX-U2, FPC3-PTX-U3
  *  FPC3-SFF-PTX
  *  LC1101, LC1102, LC1104, LC1105

This issue affects Junos OS: 

  *  all versions before 22.4R3-S8, 
  *  from 23.2 before 23.2R2-S6, 
  *  from 23.4 before 23.4R2-S6, 
  *  from 24.2 before 24.2R2-S3, 
  *  from 24.4 before 24.4R2,
  *  from 25.2 before 25.2R2.

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

## Which versions are affected by CVE-2025-30650?

It affects 1 product.


Products: Juniper Junos.

## How do I fix CVE-2025-30650?

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

## Is CVE-2025-30650 being exploited?

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

What it is: CVE-2025-30650 is a high-severity missing authorization vulnerability in Juniper Junos, published on 8 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-2025-30650 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-2025-30650/ (Markdown: https://insights.sbomify.com/CVE-2025-30650/index.md)
```

## Sources

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

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