Vulnerability in Node.js Permission Model enforcement (CVE-2026-58043)
Summary
Vulnerability in Node.js Permission Model enforcement (CVE-2026-58043). Confidential information can be exposed externally.
Original description
The description as published by the source.
A flaw in Node.js Permission Model enforcement can over-grant filesystem access across radix-tree prefix boundaries.
Under --permission, an attacker who is granted access to one path can abuse boundary handling to read from or write to paths outside the intended filesystem allowlist.
This vulnerability affects Node.js main, 22.x, 24.x, and 26.x.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
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-58043 has been found in Node.js Permission Model enforcement.
Confidential information can be exposed externally. CVSS score: 8.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Node.js Permission Model enforcement CVE-2026-58043" on the vendor's site.
CVE-2026-58043 (Node.js Permission Model enforcement) — CWE-284 / CVSS v3 8.4
Attack vector: local / no user interaction
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.
A vulnerability (CWE-284) exists in Node.js Permission Model enforcement.
Check the vendor advisory for the affected versions of Node.js Permission Model enforcement.
Severity: High (CVSS 8.4/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Node.js Permission Model enforcement を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Alpine Linux ALPINE-CVE-2026-58043 nodejs Fixed in: 22.23.2-r0
- BellSoft Alpaquita BELL-CVE-2026-58043 nodejs Fixed in: 22.23.2-r0
- Debian DEBIAN-CVE-2026-58043 nodejs Fixed in: 20.19.2+dfsg-1+deb13u3
- Ubuntu UBUNTU-CVE-2026-58043 nodejs
References
- advisory nodejs.org
- web nvd.nist.gov
- web github.com