CVE-2026-21636: Nodejs · A flaw in Node.js's permission model allows Unix Domain Socket (UDS) connections to bypass
Affects nodejsSource GCVE Database
Not known to be exploited · CVSS 5.8 Medium.
Data as of 5 Nov 2026, 00:01 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10nodejspkg:deb/ubuntu/nodejs?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 25.10nodejspkg:deb/ubuntu/nodejs?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, users should exercise caution when enabling the Node.js permission model with `--permission` and avoid using it in untrusted environments. Monitoring vendor advisories for updates is recommended.
Description
A critical vulnerability in Node.js version 25 affects the permission model controlling Unix Domain Socket (UDS) connections. When the permission model is enabled with `--permission`, attackers can bypass network restrictions even without the `--allow-net` flag by using attacker-controlled inputs to connect to arbitrary local sockets. This flaw breaks the intended security boundary, potentially allowing privilege escalation, data exposure, or local code execution. The network permissions feature was still experimental at the time of this vulnerability.