# CVE-2024-36138: Command injection in Node

> Attackers can execute arbitrary commands via malicious arguments in Node.js child_process.spawn on Windows, bypassing previous security fixes.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Sep 2024
- **Updated:** 30 Apr 2025
- **Also known as:** BIT-node-2024-36138, BIT-node-min-2024-36138, CLEANSTART-2026-FU20845, GHSA-p2ww-p57h-w5m7

## What is CVE-2024-36138?

CVE-2024-36138 is a high-severity command injection vulnerability in NodeJS Node, published on 7 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Bypass incomplete fix of CVE-2024-27980, that arises from improper handling of batch files with all possible extensions on Windows via child_process.spawn / child_process.spawnSync. A malicious command line argument can inject arbitrary commands and achieve code execution even if the shell option is not enabled.

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

## Which versions are affected by CVE-2024-36138?

2 open source packages ship an affected version, including node and node-min.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node` | Bitnami | All versions | 18.20.4, 20.15.1, 22.4.1 |
| `node-min` | Bitnami | All versions | 18.20.5, 20.18.1, 22.12.0 |

## How do I fix CVE-2024-36138?

Upgrade node to a fixed version for your release line: 18.20.4, 20.15.1 or 22.4.1.

## Is CVE-2024-36138 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36138 and fix it if it is affected.

What it is: CVE-2024-36138 is a high-severity command injection vulnerability in NodeJS Node, published on 7 Sep 2024. 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-2024-36138 in the wild and no public exploit code.

Affected packages and fixed versions:
- node (Bitnami): affected all versions; fixed in 18.20.4, 20.15.1, 22.4.1
- node-min (Bitnami): affected all versions; fixed in 18.20.5, 20.18.1, 22.12.0

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

## Sources

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

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