# CVE-2025-60006: Junos OS Evolved: OS command injection vulnerabilities fixed

> Attackers can execute unauthorized commands and elevate privileges via crafted CLI inputs in Junos OS Evolved.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/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 Oct 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-xcwm-53h2-9xwp

## What is CVE-2025-60006?

CVE-2025-60006 is a medium-severity command injection vulnerability in Juniper Junos Os Evolved, published on 9 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple instances of an Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') 

vulnerability in the CLI of Juniper Networks Junos OS Evolved could be used to elevate privileges and/or execute unauthorized commands.

When an attacker executes crafted CLI commands, the options are processed via a script in some cases. These scripts are not hardened so injected commands might be executed via the shell, which allows an attacker to perform operations, which they should not be able to do according to their assigned permissions.

This issue affects Junos OS Evolved:

  *  24.2 versions before 24.2R2-S2-EVO,
  *  24.4 versions before 24.4R2-EVO.

This issue does not affect Junos OS Evolved versions earlier than 24.2R1-EVO.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Juniper Junos Os Evolved.

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

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

## Is CVE-2025-60006 being exploited?

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

What it is: CVE-2025-60006 is a medium-severity command injection vulnerability in Juniper Junos Os Evolved, published on 9 Oct 2025. 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-60006 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-2025-60006/ (Markdown: https://insights.sbomify.com/CVE-2025-60006/index.md)
```

## Sources

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

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