cve.bz

CVE-2026-106071 nodejs node: Improper Access Control

3.6 lowEPSS 0.2%

Low (3.6) in nodejs node. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
A flaw in Node.js Permission Model filesystem enforcement can grant access to paths that do not match a wildcard `--allow-fs-read` or `--allow-fs-write` rule. When the requested path is shorter than the prefix of a wildcard grant, the radix tree lookup stops comparing early and treats the path as a match. For example, `--allow-fs-read=/etc/passwd.*` also allows reading `/etc/passwd`. This requires the wildcard grant to sit directly under the root of the permission tree, for example when it is the only grant for that scope. This is a different root cause from CVE-2026-58043. This vulnerability affects Node.js **26.x**.

Severity

CVSS 3.0

3.6 low
CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 10th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-284 Improper Access Control
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-106071 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106071?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106071?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-106071 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
nodejs nodefrom 26.12.0 through 26.12.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14nodejsno fix listedDEBIAN-CVE-2026-106071
Ubuntu24.04:LTS, 26.04:LTS, 26.10 and 5 morenodejsno fix listedUBUNTU-CVE-2026-106071
AlmaLinux8nodejs, nodejs-docs, nodejs-libs and 2 more1:24.22.1-1.module_el8.10.0+4331+0683c9c1ALSA-2026:92376
AlmaLinux8nodejs-nodemon3.1.14-2.module_el8.10.0+4250+09238ed4ALSA-2026:92376
AlmaLinux8nodejs-packaging, nodejs-packaging-bundler2021.06-6.module_el8.10.0+4086+70facd4aALSA-2026:92376
AlmaLinux8npm1:11.19.1-1.24.22.1.1.module_el8.10.0+4331+0683c9c1ALSA-2026:92376
AlmaLinux8v8-13.6-devel3:13.6.233.17-1.24.22.1.1.module_el8.10.0+4331+0683c9c1ALSA-2026:92376
AlmaLinux9nodejs, nodejs-docs, nodejs-libs and 2 more1:24.22.1-3.module_el9.8.0+333+788f3075ALSA-2026:92378
AlmaLinux9nodejs-nodemon3.1.14-3.module_el9.8.0+292+f4eaf8b2ALSA-2026:92378
AlmaLinux9nodejs-packaging, nodejs-packaging-bundler2021.06-6.module_el9.7.0+209+ecf6523eALSA-2026:92378
AlmaLinux9npm1:11.19.1-1.24.22.1.3.module_el9.8.0+333+788f3075ALSA-2026:92378
AlmaLinux9v8-13.6-devel3:13.6.233.17-1.24.22.1.3.module_el9.8.0+333+788f3075ALSA-2026:92378
Rocky Linux8nodejs-nodemon0:3.1.14-2.module+el8.10.0+40277+b1b3f89eRLSA-2026:92376
Rocky Linux8nodejs-nodemon0:3.1.14-2.module+el8.10.0+40278+50b003a3RLSA-2026:92376
Rocky Linux8nodejs-packaging0:2021.06-6.module+el8.10.0+40048+6d99f608RLSA-2026:92376
Rocky Linux8nodejs-packaging0:2021.06-6.module+el8.10.0+40171+8fa9c325RLSA-2026:92376
Rocky Linux8nodejs-packaging0:2021.06-6.module+el8.10.0+40172+38f6fdd1RLSA-2026:92376
Rocky Linux9nodejs1:24.22.1-3.module+el9.8.0+40401+e24b8c95RLSA-2026:92378
Rocky Linux9nodejs-nodemon0:3.1.14-3.module+el9.8.0+40281+14cc6568RLSA-2026:92378
Rocky Linux9nodejs-packaging0:2021.06-6.module+el9.7.0+40052+e32ea525RLSA-2026:92378
Rocky Linux9nodejs-packaging0:2021.06-6.module+el9.7.0+40153+4d595597RLSA-2026:92378
Rocky Linux9nodejs-packaging0:2021.06-6.module+el9.7.0+40165+d075e3f2RLSA-2026:92378
Rocky Linux9nodejs-packaging0:2021.06-6.module+el9.8.0+40164+8921ab53RLSA-2026:92378
Alpinev3.23, v3.24nodejs24.22.1-r0ALPINE-CVE-2026-106071
Alpinev3.24nodejs-current26.12.1-r0ALPINE-CVE-2026-106071
Azure Linux3nodejs24.22.1-0AZL-111023
Alpaquita25nodejs2626.12.1-r0BELL-CVE-2026-106071
Alpaquitastreamnodejs2626.12.1-r1BELL-CVE-2026-106071
BellSoft Hardened Containers25nodejs2626.12.1-r0BELL-CVE-2026-106071
BellSoft Hardened Containersstreamnodejs2626.12.1-r1BELL-CVE-2026-106071

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpine · Alpaquita · BellSoft Hardened Containers.

Red Hat

Red Hat rates this Low.

Red Hat's statement

This is a Low severity flaw. Red Hat rates it Low because the Permission Model is an opt-in experimental hardening feature (--permission), exploitation needs a specific wildcard grant layout (high attack complexity), and impact is limited to additional filesystem read/write within that model (Low/Low). Deployments that do not enable --permission are not exposed. The issue is confined to Node.js 26.x.

Red Hat's mitigation

If the Permission Model is unused, do not enable --permission.

When using --allow-fs-read/--allow-fs-write, avoid wildcard grants placed as the sole root-level rule; prefer explicit directory prefixes without ambiguous wildcards.

Combine application allowlists with OS confinement such as SELinux or container filesystem restrictions .

ProductPackageStateAdvisory
Red Hat Enterprise Linux 8nodejs:24-8100020261027151919.6d880403Fixed 2026-10-29RHSA-2026:92376
Red Hat Enterprise Linux 9nodejs:24-9080020261027142403.rhel9Fixed 2026-10-29RHSA-2026:92378
Red Hat Enterprise Linux 10nodejs22Not affected
Red Hat Enterprise Linux 10nodejs24Not affected
Red Hat Enterprise Linux 10nodejs26Fix deferred
Red Hat Enterprise Linux 8nodejs:22/nodejsNot affected
Red Hat Enterprise Linux 9nodejs:22/nodejsNot affected
Red Hat Enterprise Linux 9nodejs:26/nodejsFix deferred
Red Hat Hardened Imageshi/nodejsNot affected
Red Hat Hardened Imagesnodejs20Not affected
Red Hat Hardened Imagesnodejs22Not affected
Red Hat Hardened Imagesnodejs24Not affected
Red Hat Hardened Imagesnodejs25Not affected
Red Hat Hardened Imagesnodejs26Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-106071.

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).

References

Check your stackJSON