# CVE-2026-32260: Command Injection via incomplete shell metacharacter blocklist in node:child_process (bypass of CVE-2026-27190 fix)


- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 12 Mar 2026
- **Updated:** 13 Mar 2026
- **Also known as:** GHSA-4c96-w8v2-p28j

## What is CVE-2026-32260?

CVE-2026-32260 is a high-severity vulnerability in denoland deno, published on 12 Mar 2026. 

### Official description

Deno is a JavaScript, TypeScript, and WebAssembly runtime. From 2.7.0 to 2.7.1,  A command injection vulnerability exists in Deno's node:child_process polyfill (shell: true mode) that bypasses the fix for CVE-2026-27190. The two-stage argument sanitization in transformDenoShellCommand (ext/node/polyfills/internal/child_process.ts) has a priority bug: when an argument contains a $VAR pattern, it is wrapped in double quotes (L1290) instead of single quotes. Double quotes in POSIX sh do not suppress backtick command substitution, allowing injected commands to execute. An attacker who controls arguments passed to spawnSync or spawn with shell: true can execute arbitrary OS commands, bypassing Deno's permission system. This vulnerability is fixed in 2.7.2.

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

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

2 open source packages ship an affected version, including deno. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `deno` | crates.io | From 2.7.0 | 2.7.2 |
| `deno` | crates.io | From 2.7.0 | 2.7.2 |

Products: Deno Deno.

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

Upgrade deno to 2.7.2 or later.

## Is CVE-2026-32260 being exploited?

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

## Other vulnerabilities in denoland deno

- [CVE-2023-28445](https://insights.sbomify.com/CVE-2023-28445/): Deno improperly handles resizable ArrayBuffer (critical 10.0)
- [CVE-2022-24783](https://insights.sbomify.com/CVE-2022-24783/): Sandbox bypass leading to arbitrary code execution in Deno (critical 10.0)
- [CVE-2021-32619](https://insights.sbomify.com/CVE-2021-32619/): Static imports inside dynamically imported modules do not adhere to permission checks (critical 9.8)
- [CVE-2026-22863](https://insights.sbomify.com/CVE-2026-22863/): Deno node:crypto doesn't finalize cipher (critical 9.2)
- [CVE-2024-27936](https://insights.sbomify.com/CVE-2024-27936/): Deno interactive permission prompt spoofing via improper ANSI stripping (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-32260 is a high-severity vulnerability in denoland deno, published on 12 Mar 2026. 
Exploitation: There is no known exploitation of CVE-2026-32260 in the wild and no public exploit code.

Affected packages and fixed versions:
- deno (crates.io): affected from 2.7.0; fixed in 2.7.2
- deno (crates.io): affected from 2.7.0; fixed in 2.7.2

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

## Sources

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

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