CVE-2026-21636: Vulnerability in nodejs node
Node.js version 25.2.1 contains a vulnerability in its permission model that allows Unix Domain Socket (UDS) connections to bypass network restrictions when the --permission flag is enabled. This flaw permits attacker-controlled inputs to connect to arbitrary local sockets even without the --allow-net permission, breaking the intended security boundary. The issue can lead to unauthorized access to privileged local services, potentially resulting in privilege escalation or data exposure. The network permissions feature was still experimental at the time of this vulnerability.
AI Analysis
Technical Summary
CVE-2026-21636 is a medium-severity vulnerability in Node.js v25.2.1 affecting the permission model. When the --permission flag is enabled, the flaw allows connections to Unix Domain Sockets to bypass network restrictions, even if --allow-net is not granted. Attackers can use inputs such as URLs or socketPath options in net, tls, or undici/fetch modules to connect to arbitrary local sockets. This breaks the security boundary intended by the permission model and may enable access to privileged local services, leading to privilege escalation or data exposure. The network permission system was experimental during this version.
Potential Impact
The vulnerability allows unauthorized local socket connections bypassing network permission restrictions, potentially exposing privileged local services. This can lead to privilege escalation or data exposure on affected systems. There are no known exploits in the wild at the time of publication. The CVSS 3.0 base score is 5.8 (medium), reflecting network attack vector, low attack complexity, no privileges required, no user interaction, scope change, and limited confidentiality impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no patch or official fix is indicated, users should monitor the Node.js project for updates addressing this vulnerability. Until a fix is available, avoid enabling the --permission flag in environments where untrusted inputs can influence socket connections or restrict usage of affected Node.js version 25.2.1.
CVE-2026-21636: Vulnerability in nodejs node
Description
Node.js version 25.2.1 contains a vulnerability in its permission model that allows Unix Domain Socket (UDS) connections to bypass network restrictions when the --permission flag is enabled. This flaw permits attacker-controlled inputs to connect to arbitrary local sockets even without the --allow-net permission, breaking the intended security boundary. The issue can lead to unauthorized access to privileged local services, potentially resulting in privilege escalation or data exposure. The network permissions feature was still experimental at the time of this vulnerability.
CVSS v3.0
Score 5.8medium
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
CVE-2026-21636 is a medium-severity vulnerability in Node.js v25.2.1 affecting the permission model. When the --permission flag is enabled, the flaw allows connections to Unix Domain Sockets to bypass network restrictions, even if --allow-net is not granted. Attackers can use inputs such as URLs or socketPath options in net, tls, or undici/fetch modules to connect to arbitrary local sockets. This breaks the security boundary intended by the permission model and may enable access to privileged local services, leading to privilege escalation or data exposure. The network permission system was experimental during this version.
Potential Impact
The vulnerability allows unauthorized local socket connections bypassing network permission restrictions, potentially exposing privileged local services. This can lead to privilege escalation or data exposure on affected systems. There are no known exploits in the wild at the time of publication. The CVSS 3.0 base score is 5.8 (medium), reflecting network attack vector, low attack complexity, no privileges required, no user interaction, scope change, and limited confidentiality impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no patch or official fix is indicated, users should monitor the Node.js project for updates addressing this vulnerability. Until a fix is available, avoid enabling the --permission flag in environments where untrusted inputs can influence socket connections or restrict usage of affected Node.js version 25.2.1.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- hackerone
- Date Reserved
- 2026-01-01T15:00:02.339Z
- Cvss Version
- 3.0
- State
- PUBLISHED
Threat ID: 696feab04623b1157c4e3b7e
Added to database: 01/20/2026, 20:50:56 UTC
Last enriched: 07/02/2026, 23:37:24 UTC
Last updated: 09/10/2026, 19:36:52 UTC
Views: 1169
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.