# CVE-2025-60007: Junos OS: A specifically crafted 'show chassis' command causes chassisd to crash

> A local attacker can crash the chassis daemon via a crafted command, causing a temporary service outage on Juniper network devices.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/AU:Y/R:A/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:** 15 Jan 2026
- **Updated:** 16 Mar 2026
- **Also known as:** GHSA-xfq5-fxgc-9grj

## What is CVE-2025-60007?

CVE-2025-60007 is a medium-severity vulnerability in Juniper Junos, published on 15 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A NULL Pointer Dereference vulnerability in the chassis daemon (chassisd) of Juniper Networks Junos OS on MX, SRX and EX Series allows a local attacker with low privileges to cause a Denial-of-Service (DoS).

When a user executes the 'show chassis' command with specifically crafted options, chassisd will crash and restart. Due to this all components but the Routing Engine (RE) in the chassis are reinitialized, which leads to a complete service outage, which the system automatically recovers from.

This issue affects:

Junos OS on MX, SRX and EX Series,  except MX10000 Series and MX304: 

  *  all versions before 22.4R3-S8,
  *  23.2 versions before 23.2R2-S5,
  *  23.4 versions before 23.4R2-S6,
  *  24.2 versions before 24.2R2-S2,
  *  24.4 versions before 24.4R2.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Juniper Junos.

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

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

## Is CVE-2025-60007 being exploited?

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

What it is: CVE-2025-60007 is a medium-severity vulnerability in Juniper Junos, published on 15 Jan 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-60007 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-60007/ (Markdown: https://insights.sbomify.com/CVE-2025-60007/index.md)
```

## Sources

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

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