Vulnerability in Nodejs (CVE-2026-21716, CVSS 3.3)

Summary

Vulnerability in Nodejs (CVE-2026-21716). Risk of unauthorized operations or information disclosure. Exploitable via FileHandle.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-21716 has been found in Nodejs.
Attackers can target a specific entry point like FileHandle over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Nodejs CVE-2026-21716" on the vendor's site.

CVE-2026-21716 (Nodejs) — CWE-862 / CVSS v3 3.3
Attack vector: local / no user interaction
Attack surface: FileHandle
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-862) exists in Nodejs. Attackers reach the vulnerable code path via FileHandle.

📍 Affected scope

Check the vendor advisory for the affected versions of Nodejs. Attack surface: FileHandle.

🔥 Severity

Severity: Low (CVSS 3.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Nodejs' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'Nodejs' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Nodejs を grep し、稼働しているサービス・バージョンを把握する。
2
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Bitnami node

[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"20.20.2"},{"introduced":"21.0.0"},{"fixed":"22.22.2"},{"introduced":"23.0.0"},{"fixed":"24.14.1"},{"introduced":"25.0.0"},{"fixed":"25.8.2"}]}]

Bitnami node-min

[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"20.20.2"},{"introduced":"21.0.0"},{"fixed":"22.22.2"},{"introduced":"23.0.0"},{"fixed":"24.14.1"},{"introduced":"25.0.0"},{"fixed":"25.8.2"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

Alpine Linux ALPINE-CVE-2026-21716 nodejs Fixed in: 22.22.2-r0
Debian DEBIAN-CVE-2026-21716 nodejs Fixed in: 20.19.2+dfsg-1+deb13u2
Ubuntu UBUNTU-CVE-2026-21716 nodejs

References

advisory nvd.nist.gov
advisory github.com
web nodejs.org