# CVE-2026-21716: Security feature bypass in node

> Attackers can bypass Node.js permission model restrictions to modify file permissions and ownership via promise-based FileHandle methods.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Mar 2026
- **Updated:** 31 Mar 2026
- **Also known as:** ALPINE-CVE-2026-21716, AZL-81236, AZL-81254, BELL-CVE-2026-21716, BIT-node-2026-21716, BIT-node-min-2026-21716, CLEANSTART-2026-JO53720, DEBIAN-CVE-2026-21716, GHSA-22vj-v4r3-878v, MINI-2rff-xj2m-crvv, MINI-5h9w-wqhw-862q, MINI-c3g6-jq7j-4r3h, MINI-frq3-84rv-2mhv, MINI-gv9f-9gp6-rwmj, MINI-hp5w-5g67-25c3, MINI-q7xg-h7f6-v6q3, UBUNTU-CVE-2026-21716

## What is CVE-2026-21716?

CVE-2026-21716 is a low-severity vulnerability in Nodejs Node.js, published on 30 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An incomplete fix for CVE-2024-36137 leaves `FileHandle.chmod()` and `FileHandle.chown()` in the promises API without the required permission checks, while their callback-based equivalents (`fs.fchmod()`, `fs.fchown()`) were correctly patched.

As a result, code running under `--permission` with restricted `--allow-fs-write` can still use promise-based `FileHandle` methods to modify file permissions and ownership on already-open file descriptors, bypassing the intended write restrictions.

This vulnerability affects **20.x, 22.x, 24.x, and 25.x** processes using the Permission Model where `--allow-fs-write` is intentionally restricted.

Weakness: CWE-862 (Missing Authorization)

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

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 | 20.20.2, 22.22.2, 24.14.1, 25.8.2 |
| `node-min` | Bitnami | All versions | 20.20.2, 22.22.2, 24.14.1, 25.8.2 |

Products: Nodejs Node.js.

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

Upgrade node to a fixed version for your release line: 20.20.2, 22.22.2, 24.14.1 or 25.8.2.

## Is CVE-2026-21716 being exploited?

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

## Other vulnerabilities in Nodejs Node.js

- [CVE-2023-32002](https://insights.sbomify.com/CVE-2023-32002/): Security feature bypass in Node (critical 9.8)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-21716 is a low-severity vulnerability in Nodejs Node.js, published on 30 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-21716 in the wild and no public exploit code.

Affected packages and fixed versions:
- node (Bitnami): affected all versions; fixed in 20.20.2, 22.22.2, 24.14.1, 25.8.2
- node-min (Bitnami): affected all versions; fixed in 20.20.2, 22.22.2, 24.14.1, 25.8.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-21716/ (Markdown: https://insights.sbomify.com/CVE-2026-21716/index.md)
```

## Sources

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

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