# CVE-2023-32002: Security feature bypass in Node

> Attackers can bypass Node.js experimental policy restrictions using Module._load to load unauthorized modules, affecting users of this experimental feature.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/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:** 21 Aug 2023
- **Updated:** 2 Jul 2025
- **Also known as:** ALPINE-CVE-2023-32002, AZL-27940, AZL-27942, BIT-node-2023-32002, BIT-node-min-2023-32002, CLEANSTART-2026-JH69025, CLEANSTART-2026-SI18648, DEBIAN-CVE-2023-32002, GHSA-9m48-r3w4-x35v, UBUNTU-CVE-2023-32002

## What is CVE-2023-32002?

CVE-2023-32002 is a critical vulnerability in Nodejs Node.js, published on 21 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The use of `Module._load()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module.

This vulnerability affects all users using the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x.

Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2023-32002?

2 open source packages ship an affected version, including node and node-min. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node` | Bitnami | All versions | 16.20.2, 18.17.1, 20.5.1 |
| `node-min` | Bitnami | All versions | 16.20.2, 18.17.1, 20.5.1 |

Products: Nodejs Node.js.

## How do I fix CVE-2023-32002?

Upgrade node to a fixed version for your release line: 16.20.2, 18.17.1 or 20.5.1.

## Is CVE-2023-32002 being exploited?

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

## Other vulnerabilities in Nodejs Node.js

- [CVE-2016-6303](https://insights.sbomify.com/CVE-2016-6303/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-15896](https://insights.sbomify.com/CVE-2017-15896/): Security feature bypass in Node.js (critical 9.1)
- [CVE-2018-7160](https://insights.sbomify.com/CVE-2018-7160/): Server-side request forgery in Node.js (high 8.8)
- [CVE-2018-12120](https://insights.sbomify.com/CVE-2018-12120/): Misconfiguration in Node.js (high 8.1)
- [CVE-2024-21891](https://insights.sbomify.com/CVE-2024-21891/): Path traversal in Node (high 7.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-32002 and fix it if it is affected.

What it is: CVE-2023-32002 is a critical vulnerability in Nodejs Node.js, published on 21 Aug 2023. 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-2023-32002 in the wild and no public exploit code.

Affected packages and fixed versions:
- node (Bitnami): affected all versions; fixed in 16.20.2, 18.17.1, 20.5.1
- node-min (Bitnami): affected all versions; fixed in 16.20.2, 18.17.1, 20.5.1

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

## Sources

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

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