CVE-2026-58043 is an improper path-boundary enforcement flaw in the Node.js Permission Model. When Node.js is run with --permission, radix-tree prefix handling can over-grant filesystem permissions across intended path boundaries. Code granted access to an allowed path can consequently access filesystem paths outside the configured allowlist.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
39 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Node.js Permission Model enforcement flaw that permits unauthorized filesystem access.
A Miracle Linux 8 Node.js-related vulnerability addressed by advisory AXSA-2026-1771. It is rated CVSS v3.0 7.7 and requires local access and low privileges, with high confidentiality and integrity impact across a changed scope.
A high-impact local vulnerability affecting Miracle Linux 8 Node.js-related packages. The supplied CVSS v3 vector indicates low attack complexity, low privileges required, no user interaction, scope changed, and high confidentiality and integrity impact; availability impact is none.
A locally exploitable vulnerability in Oracle Linux 10 Node.js 24 packages. Based on the supplied CVSS vector, exploitation requires low privileges and no user interaction, can cross a security scope boundary, and has high confidentiality and integrity impact.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.