CVE-2026-21711: Vulnerability in nodejs node
A flaw in Node.js Permission Model network enforcement leaves Unix Domain Socket (UDS) server operations without the required permission checks, while all comparable network paths correctly enforce them. As a result, code running under `--permission` without `--allow-net` can create and expose local IPC endpoints, allowing communication with other processes on the same host outside of the intended network restriction boundary. This vulnerability affects Node.js **25.x** processes using the Permission Model where `--allow-net` is intentionally omitted to restrict network access. Note that `--allow-net` is currently an experimental feature.
AI Analysis
Technical Summary
This vulnerability in Node.js arises from incomplete permission enforcement in the Permission Model for Unix Domain Socket server operations. While network access is intended to be restricted when running Node.js with --permission but without --allow-net, UDS server operations do not enforce these restrictions, allowing local IPC endpoints to be created and exposed. This breaks the intended network isolation boundary. The issue affects Node.js versions from 4.0 up to 25.8.1 where the experimental --allow-net flag is used.
Potential Impact
An attacker or untrusted code running with limited network permissions can create and expose local IPC endpoints via Unix Domain Sockets, potentially enabling unauthorized inter-process communication on the same host. This could lead to information disclosure or interference with other local processes. The CVSS score of 5.3 reflects a medium severity impact with local attack vector, low attack complexity, and limited privileges required.
Mitigation Recommendations
Patch status is not yet confirmed — no official patch or remediation guidance is provided in the available data. Users should monitor the Node.js vendor advisories for updates regarding a fix. Until then, be cautious when using the experimental --allow-net feature and consider restricting or auditing local IPC usage in Node.js processes to mitigate potential exposure.
CVE-2026-21711: Vulnerability in nodejs node
Description
A flaw in Node.js Permission Model network enforcement leaves Unix Domain Socket (UDS) server operations without the required permission checks, while all comparable network paths correctly enforce them. As a result, code running under `--permission` without `--allow-net` can create and expose local IPC endpoints, allowing communication with other processes on the same host outside of the intended network restriction boundary. This vulnerability affects Node.js **25.x** processes using the Permission Model where `--allow-net` is intentionally omitted to restrict network access. Note that `--allow-net` is currently an experimental feature.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability in Node.js arises from incomplete permission enforcement in the Permission Model for Unix Domain Socket server operations. While network access is intended to be restricted when running Node.js with --permission but without --allow-net, UDS server operations do not enforce these restrictions, allowing local IPC endpoints to be created and exposed. This breaks the intended network isolation boundary. The issue affects Node.js versions from 4.0 up to 25.8.1 where the experimental --allow-net flag is used.
Potential Impact
An attacker or untrusted code running with limited network permissions can create and expose local IPC endpoints via Unix Domain Sockets, potentially enabling unauthorized inter-process communication on the same host. This could lead to information disclosure or interference with other local processes. The CVSS score of 5.3 reflects a medium severity impact with local attack vector, low attack complexity, and limited privileges required.
Mitigation Recommendations
Patch status is not yet confirmed — no official patch or remediation guidance is provided in the available data. Users should monitor the Node.js vendor advisories for updates regarding a fix. Until then, be cautious when using the experimental --allow-net feature and consider restricting or auditing local IPC usage in Node.js processes to mitigate potential exposure.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- hackerone
- Date Reserved
- 2026-01-04T15:00:06.574Z
- Cvss Version
- 3.0
- State
- PUBLISHED
Threat ID: 69cacda7e6bfc5ba1d6188a5
Added to database: 3/30/2026, 7:23:19 PM
Last enriched: 4/7/2026, 9:42:52 AM
Last updated: 5/15/2026, 7:54:45 AM
Views: 93
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.