Bug 2560018 (CVE-2026-106071) - CVE-2026-106071 nodejs: nodejs: Permission model bypass via wildcard path matching flaw
Summary: CVE-2026-106071 nodejs: nodejs: Permission model bypass via wildcard path mat...
Keywords:
Status: NEW
Alias: CVE-2026-106071
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2560634
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-23 16:22 UTC by OSIDB Bzimport
Modified: 2026-10-29 22:29 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:92376 0 None None None 2026-10-29 14:21:09 UTC
Red Hat Product Errata RHSA-2026:92378 0 None None None 2026-10-29 22:29:52 UTC

Description OSIDB Bzimport 2026-10-23 16:22:10 UTC
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**.

Comment 3 Jon Orris 2026-10-29 14:21:08 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:92376 https://access.redhat.com/errata/RHSA-2026:92376

Comment 4 Jon Orris 2026-10-29 22:29:51 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:92378 https://access.redhat.com/errata/RHSA-2026:92378


Note You need to log in before you can comment on or make changes to this bug.