Loading vulnerability…
Node.js Permission Model Filesystem Allowlist Bypass
CVE-2026-58043 is an authorization flaw in Node.js Permission Model filesystem enforcement. Improper handling of radix-tree prefix boundaries can cause a filesystem permission grant to extend beyond its intended path boundary. When Node.js runs with --permission, an attacker granted access to one path can exploit this behavior to read from or write to paths outside the configured filesystem allowlist. Affected release lines include Node.js main, 22.x, 24.x, and 26.x.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation violates application-level filesystem isolation, allowing unauthorized disclosure or modification of files accessible to the Node.js operating-system account but excluded by the Permission Model allowlist. The vulnerability has high confidentiality and integrity impact and can cross the intended security boundary. No direct availability impact is identified.
If you can’t patch tonight, do this now.
Until patched, do not rely on the affected Permission Model as the sole filesystem isolation boundary for untrusted code. Avoid executing untrusted workloads in affected processes where feasible. Restrict the process account's operating-system filesystem permissions, isolate workloads with containers or other OS-level sandboxing, and minimize filesystem grants. These measures limit exposure but do not correct the authorization flaw.
Patch, then assume compromise.
Install the security-fixed Node.js packages appropriate to the deployed distribution and release branch, then restart affected Node.js services. SUSE identifies fixed package baselines of Node.js 22.23.2, 24.18.1, and 26.5.1, with distribution-specific release suffixes. For Chainguard nodejs-22 and related packages, update to 22.23.2-r0 or later. RHEL 8 Node.js 24 users should apply RHSA-2026:62583, which supplies updated Node.js 24.19.0 packages. Use the applicable vendor advisory to determine the exact package build required.
No validated public exploits yet. Hidden: 3 rejected by Mallory's analysis as not a working exploit.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
55 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.