# CVE-2026-103473: Deno 2.7.0 through 2.9.7 Command Injection via node:child_process

> Attackers can execute arbitrary OS commands on Windows by exploiting improper shell argument escaping in the node:child_process module.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-m6mv-f8h2-2w86

## What is CVE-2026-103473?

CVE-2026-103473 is a critical command injection vulnerability in denoland deno, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Deno versions 2.7.0 through 2.9.7 on Windows contain a command injection vulnerability in node:child_process where shell arguments are escaped for the wrong shell type. Attackers can inject OS commands by passing untrusted arguments with the shell option, allowing arbitrary command execution with Deno process privileges.

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

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


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

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

## Is CVE-2026-103473 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103473 is a critical command injection vulnerability in denoland deno, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-103473 in the wild and no public exploit code.

Affected product: denoland deno. 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-2026-103473/ (Markdown: https://insights.sbomify.com/CVE-2026-103473/index.md)
```

## Sources

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

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