# CVE-2025-66032: Claude Code Command Validation Bypass Allows Arbitrary Code Execution

> Attackers can bypass read-only validation to execute arbitrary code by injecting malicious shell commands into the context window.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Dec 2025
- **Updated:** 3 Dec 2025
- **Also known as:** GHSA-xq4m-mc3c-vvg3

## What is CVE-2025-66032?

CVE-2025-66032 is a high-severity command injection vulnerability in anthropics claude-code, published on 3 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Claude Code is an agentic coding tool. Prior to 1.0.93, Due to errors in parsing shell commands related to $IFS and short CLI flags, it was possible to bypass the Claude Code read-only validation and trigger arbitrary code execution. Reliably exploiting this requires the ability to add untrusted content into a Claude Code context window. This vulnerability is fixed in 1.0.93.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

2 open source packages ship an affected version, including @anthropic-ai/claude-code. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@anthropic-ai/claude-code` | npm | All versions | 1.0.93 |
| `@anthropic-ai/claude-code` | npm | All versions | 1.0.93 |

Products: Anthropic Claude Code.

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

Upgrade @anthropic-ai/claude-code to 1.0.93 or later.

## Is CVE-2025-66032 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66032 exists.

## Other vulnerabilities in anthropics claude-code

- [CVE-2025-64755](https://insights.sbomify.com/CVE-2025-64755/): @anthropic-ai/claude-code has Sed Command Validation Bypass that Allows Arbitrary File Writes (high 8.7)
- [CVE-2025-59536](https://insights.sbomify.com/CVE-2025-59536/): Claude Code's startup trust dialog could lead to Command Execution attack (high 8.7)
- [CVE-2025-58764](https://insights.sbomify.com/CVE-2025-58764/): Claude Code rg command had Command Injection that allowed bypass of user approval prompt for command execution (high 8.7)
- [CVE-2025-59041](https://insights.sbomify.com/CVE-2025-59041/): Claude Code vulnerable to arbitrary code execution caused by maliciously configured git email (high 8.7)
- [CVE-2025-54795](https://insights.sbomify.com/CVE-2025-54795/): Claude Code echo command allowed bypass of user approval prompt for command execution (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-66032 and fix it if it is affected.

What it is: CVE-2025-66032 is a high-severity command injection vulnerability in anthropics claude-code, published on 3 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66032 exists.

Affected packages and fixed versions:
- @anthropic-ai/claude-code (npm): affected all versions; fixed in 1.0.93
- @anthropic-ai/claude-code (npm): affected all versions; fixed in 1.0.93

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-66032/ (Markdown: https://insights.sbomify.com/CVE-2025-66032/index.md)
```

## Sources

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

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