A flaw in Node.js Permission Model network enforcement leaves Unix Domain Socket (UDS) server operations without the required permission checks,… (CVE-2026-21711)
A vulnerability in Node.js 25.x Permission Model network enforcement allows Unix Domain Socket (UDS) server operations to bypass required permission checks. This flaw enables code running with the permission flag `--permission` but without `--allow-net` to create and expose local IPC endpoints, circumventing intended network restrictions. The issue affects Node.js versions 3.0 and 25.0.0 up to but not including 25.8.2. The `--allow-net` flag is experimental. A patch is available to address this vulnerability.
AI Analysis
Technical Summary
Node.js contains a flaw in its Permission Model network enforcement where Unix Domain Socket (UDS) server operations do not enforce permission checks as strictly as other network paths. Specifically, when running Node.js processes with the `--permission` flag but without the `--allow-net` flag, local IPC endpoints can be created and exposed via UDS, allowing communication with other local processes outside the intended network restriction boundary. This affects Node.js versions 3.0 and all 25.x versions from 25.0.0 up to but excluding 25.8.2. The vulnerability is tracked as CVE-2026-21711 and is classified under CWE-284 (Improper Access Control). A patch is available to fix this issue.
Potential Impact
The vulnerability allows processes running Node.js with restricted network permissions (omitting `--allow-net`) to bypass these restrictions by creating Unix Domain Socket servers that communicate locally. This could lead to unintended inter-process communication on the same host, potentially violating security boundaries intended by the permission model. There are no known exploits in the wild at this time.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade Node.js to version 25.8.2 or later where the issue is fixed. Until patched, avoid relying solely on the `--permission` flag without `--allow-net` to restrict network access, as the current implementation does not enforce permissions correctly for UDS server operations.
A flaw in Node.js Permission Model network enforcement leaves Unix Domain Socket (UDS) server operations without the required permission checks,… (CVE-2026-21711)
Description
A vulnerability in Node.js 25.x Permission Model network enforcement allows Unix Domain Socket (UDS) server operations to bypass required permission checks. This flaw enables code running with the permission flag `--permission` but without `--allow-net` to create and expose local IPC endpoints, circumventing intended network restrictions. The issue affects Node.js versions 3.0 and 25.0.0 up to but not including 25.8.2. The `--allow-net` flag is experimental. A patch is available to address this vulnerability.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Node.js contains a flaw in its Permission Model network enforcement where Unix Domain Socket (UDS) server operations do not enforce permission checks as strictly as other network paths. Specifically, when running Node.js processes with the `--permission` flag but without the `--allow-net` flag, local IPC endpoints can be created and exposed via UDS, allowing communication with other local processes outside the intended network restriction boundary. This affects Node.js versions 3.0 and all 25.x versions from 25.0.0 up to but excluding 25.8.2. The vulnerability is tracked as CVE-2026-21711 and is classified under CWE-284 (Improper Access Control). A patch is available to fix this issue.
Potential Impact
The vulnerability allows processes running Node.js with restricted network permissions (omitting `--allow-net`) to bypass these restrictions by creating Unix Domain Socket servers that communicate locally. This could lead to unintended inter-process communication on the same host, potentially violating security boundaries intended by the permission model. There are no known exploits in the wild at this time.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade Node.js to version 25.8.2 or later where the issue is fixed. Until patched, avoid relying solely on the `--permission` flag without `--allow-net` to restrict network access, as the current implementation does not enforce permissions correctly for UDS server operations.
Technical Details
- Gcve Source
- db.gcve.eu
- Csaf Category
- csaf_vex
- Csaf Version
- 2.0
- Publisher
- Microsoft Security Response Center
- Advisory Id
- msrc_CVE-2026-21711
- Cve Count
- 1
- State
- PUBLISHED
Threat ID: 6a1ca15be29bf47b505e2160
Added to database: 05/31/2026, 21:00:11 UTC
Last enriched: 09/08/2026, 15:18:21 UTC
Last updated: 09/11/2026, 22:06:32 UTC
Views: 137
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.