CVE-2026-106071

A flaw was found in the Node.js Permission Model. Wildcard --allow-fs-read or --allow-fs-write rules can grant access to paths that do not match the intended wildcard when the requested path is shorter than the wildcard prefix and the radix-tree lookup stops comparing early. For example, --allow-fs-read=/etc/passwd.* may also allow 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 and affects the Node.js 26.x line.

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.

The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.

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 .