CVE-2026-21711

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: 2026-03-30 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Awaiting Analysis，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-21711 is rated Low Risk (22.8/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.15%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-21711

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.01% 0.15% +0.14%
2 2026-03-31 — 0.01% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-21711

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.0 MEDIUM
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.8 3.4 [email protected]

Weakness enumeration for CVE-2026-21711

OS Trackers for CVE-2026-21711

vendor priority summary link
alpine — CVE-2026-21711: 1 source package rows (nodejs); 1 state rows across 1 repos (edge-main); fixed 1, open 0. https://security.alpinelinux.org/vuln/CVE-2026-21711
debian unimportant CVE-2026-21711 unimportant priority: Debian including 1 source packages (nodejs), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2026-21711
redhat medium — https://access.redhat.com/security/cve/CVE-2026-21711
suse medium CVE-2026-21711 severity moderate: SUSE including 59 source package names (corepack20, corepack22, …), 165 product×package rows across 20 product lines (SUSE Liberty Linux 8, SUSE Liberty Linux 9, … (20 product lines)): Known Not Affected 145, Fixed 20. https://www.suse.com/security/cve/CVE-2026-21711/
ubuntu medium CVE-2026-21711 medium priority: Ubuntu including 1 source packages (nodejs), 8 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): needs-triage 7, not-affected 1. https://ubuntu.com/security/CVE-2026-21711

Affected software / configurations for CVE-2026-21711

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-21711

cvelogic Threat Intelligence