Node.js Permission Model UDS permission check bypass
CVE-2026-21711 is a medium-severity authorization bypass in the Node.js Permission Model affecting Node.js 25.x. When the experimental Permission Model is enabled with --permission and network access is intentionally not granted via --allow-net, Node.js correctly enforces permission checks for comparable network operations but fails to enforce them for Unix Domain Socket (UDS) server bind/listen operations. As a result, code running in a supposedly network-restricted process can still create and expose local IPC endpoints over UDS, bypassing the intended network restriction boundary and enabling unauthorized local inter-process communication with other processes on the same host.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
--allow-net. This undermines the security guarantees of the permission boundary, enabling unauthorized local IPC with other host processes. Depending on the application design and local environment, this may permit data exchange with trusted local services, policy bypass, and expansion of the attack surface beyond what operators intended when disabling network access.Mitigation
If you can’t patch tonight, do this now.
--permission is enabled but --allow-net is omitted if local socket creation would be security-relevant. Apply OS-level isolation controls as compensating measures, such as filesystem and runtime sandboxing that restrict socket path creation and inter-process communication, and minimize exposure to local services reachable over UDS.Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
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.
Recent activity
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
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.