CVE-2026-21711: A flaw in Node.js Permission Model network enforcement leaves Unix Domain Socket (UDS) server operations without the required permission che
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: nodejs node 10.*, 11.*, 12.*.
Low priority for now. Upgrade to nodejs node 10.*, 11.*, 12.* or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 30, 2026
- Updated
- Aug 19, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-284
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · hackerone
- 5.3
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| nodejs | node.js | cpe:2.3:a:nodejs:node.js |
Using node.js? Add it to your stack and be the first to know about CVEs like this one. (Node.js)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nodejs node.jsbefore 20.0.0
- nodejs node.js25.0.0 and later · up to 25.8.1 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.
nodejs node
- 25.8.1 and later · up to and including 25.8.1affected · semver
- 4.0 and later · before 4.*affected · semver
- 5.0 and later · before 5.*affected · semver
- 6.0 and later · before 6.*affected · semver
- 7.0 and later · before 7.*affected · semver
- 8.0 and later · before 8.*affected · semver
- 9.0 and later · before 9.*affected · semver
- 10.0 and later · before 10.*affected · semver
- 11.0 and later · before 11.*affected · semver
- 12.0 and later · before 12.*affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | nodejs24-docs | before 1:24.14.1-2.el10_1 | 1:24.14.1-2.el10_1 |
| AlmaLinux:10 | nodejs24-npm | before 1:11.11.0-1.24.14.1.2.el10_1 | 1:11.11.0-1.24.14.1.2.el10_1 |
| AlmaLinux:8 | nodejs | before 1:24.14.1-2.module_el8.10.0+4160+4819ac42 | 1:24.14.1-2.module_el8.10.0+4160+4819ac42 |
| AlmaLinux:8 | nodejs-devel | before 1:24.14.1-2.module_el8.10.0+4160+4819ac42 | 1:24.14.1-2.module_el8.10.0+4160+4819ac42 |
| AlmaLinux:8 | nodejs-docs | before 1:24.14.1-2.module_el8.10.0+4160+4819ac42 | 1:24.14.1-2.module_el8.10.0+4160+4819ac42 |
| AlmaLinux:8 | nodejs-full-i18n | before 1:24.14.1-2.module_el8.10.0+4160+4819ac42 | 1:24.14.1-2.module_el8.10.0+4160+4819ac42 |
| AlmaLinux:8 | nodejs-libs | before 1:24.14.1-2.module_el8.10.0+4160+4819ac42 | 1:24.14.1-2.module_el8.10.0+4160+4819ac42 |
| AlmaLinux:8 | nodejs-nodemon | before 3.0.3-1.module_el8.10.0+4061+f8ceeab9 | 3.0.3-1.module_el8.10.0+4061+f8ceeab9 |
| AlmaLinux:8 | nodejs-packaging | before 2021.06-6.module_el8.10.0+4086+70facd4a | 2021.06-6.module_el8.10.0+4086+70facd4a |
| AlmaLinux:8 | nodejs-packaging-bundler | before 2021.06-6.module_el8.10.0+4086+70facd4a | 2021.06-6.module_el8.10.0+4086+70facd4a |
| AlmaLinux:8 | npm | before 1:11.11.0-1.24.14.1.2.module_el8.10.0+4160+4819ac42 | 1:11.11.0-1.24.14.1.2.module_el8.10.0+4160+4819ac42 |
| AlmaLinux:8 | v8-13.6-devel | before 3:13.6.233.17-1.24.14.1.2.module_el8.10.0+4160+4819ac42 | 3:13.6.233.17-1.24.14.1.2.module_el8.10.0+4160+4819ac42 |
| AlmaLinux:9 | nodejs | before 1:24.14.1-2.module_el9.7.0+222+ef1c61e1 | 1:24.14.1-2.module_el9.7.0+222+ef1c61e1 |
| AlmaLinux:9 | nodejs-devel | before 1:24.14.1-2.module_el9.7.0+222+ef1c61e1 | 1:24.14.1-2.module_el9.7.0+222+ef1c61e1 |
| AlmaLinux:9 | nodejs-docs | before 1:24.14.1-2.module_el9.7.0+222+ef1c61e1 | 1:24.14.1-2.module_el9.7.0+222+ef1c61e1 |
| AlmaLinux:9 | nodejs-full-i18n | before 1:24.14.1-2.module_el9.7.0+222+ef1c61e1 | 1:24.14.1-2.module_el9.7.0+222+ef1c61e1 |
| AlmaLinux:9 | nodejs-libs | before 1:24.14.1-2.module_el9.7.0+222+ef1c61e1 | 1:24.14.1-2.module_el9.7.0+222+ef1c61e1 |
| AlmaLinux:9 | nodejs-nodemon | before 3.0.3-3.module_el9.7.0+209+ecf6523e | 3.0.3-3.module_el9.7.0+209+ecf6523e |
| AlmaLinux:9 | nodejs-packaging | before 2021.06-6.module_el9.7.0+209+ecf6523e | 2021.06-6.module_el9.7.0+209+ecf6523e |
| AlmaLinux:9 | nodejs-packaging-bundler | before 2021.06-6.module_el9.7.0+198+8bf605ba | 2021.06-6.module_el9.7.0+198+8bf605ba |
| AlmaLinux:9 | npm | before 1:11.11.0-1.24.14.1.2.module_el9.7.0+222+ef1c61e1 | 1:11.11.0-1.24.14.1.2.module_el9.7.0+222+ef1c61e1 |
| AlmaLinux:9 | v8-13.6-devel | before 3:13.6.233.17-1.24.14.1.2.module_el9.7.0+222+ef1c61e1 | 3:13.6.233.17-1.24.14.1.2.module_el9.7.0+222+ef1c61e1 |
| Red Hat:enterprise_linux:10.1 | nodejs24 | before 1:24.14.1-2.el10_1 | 1:24.14.1-2.el10_1 |
| Red Hat:enterprise_linux:10.1 | nodejs24-debuginfo | before 1:24.14.1-2.el10_1 | 1:24.14.1-2.el10_1 |
+38
Same product
nodejs: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-15605HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed56Plan
- CVE-2021-22883Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to a denial of service attack when too many connection attempts with an 53Plan
- CVE-2021-22930Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to a use after free attack where an attacker might be able to exploit the memory c50Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-21712Mar 30, 2026 · A flaw in Node.js URL processing causes an assertion failure in native code when `url.format()` is called with a malformed internationalized26Monitor
- ← EarlierCVE-2026-21710Mar 30, 2026 · A flaw in Node.js HTTP request handling causes an uncaught `TypeError` when a request is received with a header named `__proto__` and the ap38Monitor
- Later →CVE-2026-21713Mar 30, 2026 · A flaw in Node.js HMAC verification uses a non-constant-time comparison when validating user-provided signatures, potentially leaking timing23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| nodejs node | 10.* | Vendor (CNA) |
| nodejs node | 11.* | Vendor (CNA) |
| nodejs node | 12.* | Vendor (CNA) |
| nodejs node | 13.* | Vendor (CNA) |
| nodejs node | 14.* | Vendor (CNA) |
| nodejs node | 15.* | Vendor (CNA) |
| nodejs node | 16.* | Vendor (CNA) |
| nodejs node | 17.* | Vendor (CNA) |
| nodejs node | 18.* | Vendor (CNA) |
| nodejs node | 19.* | Vendor (CNA) |
| nodejs node | 4.* | Vendor (CNA) |
| nodejs node | 5.* | Vendor (CNA) |
| nodejs node | 6.* | Vendor (CNA) |
| nodejs node | 7.* | Vendor (CNA) |
| nodejs node | 8.* | Vendor (CNA) |
| nodejs node | 9.* | Vendor (CNA) |
| almalinux:nodejs | 1:24.14.1-2.module_el9.7.0+222+ef1c61e1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:nodejs-devel | 1:24.14.1-2.module_el9.7.0+222+ef1c61e1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:nodejs-docs | 1:24.14.1-2.module_el9.7.0+222+ef1c61e1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:nodejs-full-i18n | 1:24.14.1-2.module_el9.7.0+222+ef1c61e1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:nodejs-libs | 1:24.14.1-2.module_el9.7.0+222+ef1c61e1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:nodejs-nodemon | 3.0.3-3.module_el9.7.0+209+ecf6523e · AlmaLinux:9 | Package registry (OSV) |
| almalinux:nodejs-packaging | 2021.06-6.module_el9.7.0+209+ecf6523e · AlmaLinux:9 | Package registry (OSV) |
| almalinux:nodejs-packaging-bundler | 2021.06-6.module_el9.7.0+198+8bf605ba · AlmaLinux:9 | Package registry (OSV) |
| almalinux:nodejs24-docs | 1:24.14.1-2.el10_1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs24-npm | 1:11.11.0-1.24.14.1.2.el10_1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:npm | 1:11.11.0-1.24.14.1.2.module_el9.7.0+222+ef1c61e1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:v8-13.6-devel | 3:13.6.233.17-1.24.14.1.2.module_el9.7.0+222+ef1c61e1 · AlmaLinux:9 | Package registry (OSV) |
| red hat:nodejs | 1:24.14.1-2.module+el9.7.0+24166+51c9666b · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:nodejs-debuginfo | 1:24.14.1-2.module+el9.7.0+24166+51c9666b · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+13
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-2163669 days apartA flaw in Node.js's permission model allows Unix Domain Socket (UDS) connections to bypass network restrictions when `--permission` is enabl40Plan
- CVE-2026-4893088 days apartA flaw in Node.js TLS hostname handling can cause Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation i39Monitor
- CVE-2026-58043122 days apartA flaw in Node.js Permission Model enforcement can over-grant filesystem access across radix-tree prefix boundaries.33Monitor
- CVE-2026-4861780 days apartA flaw in Node.js Permission Model enforcement allows Bypass via `process.report.writeReport()` Path Misvalidation.32Monitor
- CVE-2026-4892888 days apartA inconsistency in Node.js hostname matching can cause a trust-policy bypass in multi-context mTLS setups.21Monitor
- CVE-2026-4893688 days apartA flaw in Node.js Permission API can cause a local server to be started (via a Unix domain socket), even without the `--allow-net` permissio13Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-284 · Improper Access ControlCVSS vector
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Embedding Scripts within ScriptsCAPEC-19likelihood: High · High
- Malicious Logic InsertionCAPEC-441likelihood: Medium · High
- Modification of Windows Service ConfigurationCAPEC-478likelihood: Low · High
- Malicious Root CertificateCAPEC-479likelihood: Low · Low
- Intent SpoofCAPEC-502
- WebView ExposureCAPEC-503
- Data Injected During ConfigurationCAPEC-536likelihood: Low · High
- Incomplete Data Deletion in a Multi-Tenant EnvironmentCAPEC-546likelihood: Low · Medium
ATT&CK techniques
- RootkitT1014
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Initialization ScriptsT1037
- Taint shared contentT1080
- Server Software Component: Terminal Services DLLT1505.005
- Pre-OS Boot:BootkitT1542.003
- Create or Modify System ProcessT1543
- Create or Modify System Process: Launch AgentT1543.001
- Create or Modify System Process:Windows ServiceT1543.003
- Create or Modify System Process: Launch DaemonT1543.004
- Event Triggered Execution:Change Default File AssociationT1546.001
- Event Triggered Execution:.bash_profile and .bashrcT1546.004
- Event Triggered Execution: Accessibility FeaturesT1546.008
- Event Triggered Execution: Installer PackagesT1546.016
- Boot or Logon Autostart ExecutionT1547
- Boot or Logon Autostart Execution:Kernel Modules and ExtensionsT1547.006
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.