CVE-2026-21711

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2026-03-30. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

March 30, 2026

Last Modified

August 19, 2026

Advisory Details (1)

Auto-updated Aug 6, 2026
No patch confirmed yet.
generic

Node.js — Tuesday, March 24, 2026 Security Releases

https://nodejs.org/en/blog/vulnerability/march-2026-security-releases

Vendor Advisories for CVE-2026-21711(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnodejs24-1:24.14.1-2.el10_12026-04-13redhat
redhatnodejs:24-8100020260408131901.6d8804032026-04-13redhat
redhatnodejs:24-9070020260402152654.rhel92026-04-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-16 14:07 UTCEPSS rescore
  3. 2026-09-16 05:15 UTCEPSS rescore
  4. 2026-09-13 16:47 UTCEPSS rescore
  5. 2026-09-12 15:01 UTCEPSS rescore
  6. 2026-09-11 14:52 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-08 22:00 UTCEPSS rescore
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-06 03:00 UTCOSV refresh
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-01 13:53 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:48 UTCEPSS rescore
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-19 17:03 UTCEPSS rescore
  25. 2026-08-19 14:04 UTCEG score recompute
Show 55 more
  1. 2026-08-19 14:04 UTCVendor advisory
  2. 2026-08-19 14:03 UTCGHSA enrichment
  3. 2026-08-18 13:48 UTCEPSS rescore
  4. 2026-08-17 13:47 UTCEPSS rescore
  5. 2026-08-16 14:56 UTCEPSS rescore
  6. 2026-08-16 09:45 UTCEG score recompute
  7. 2026-08-16 09:45 UTCVendor advisory
  8. 2026-08-16 09:45 UTCGHSA enrichment
  9. 2026-08-16 02:14 UTCEPSS rescore
  10. 2026-08-15 01:30 UTCEPSS rescore
  11. 2026-08-14 06:08 UTCEG score recompute
  12. 2026-08-14 06:08 UTCVendor advisory
  13. 2026-08-14 06:08 UTCGHSA enrichment
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-12 20:29 UTCEG score recompute
  16. 2026-08-12 20:29 UTCVendor advisory
  17. 2026-08-12 20:29 UTCGHSA enrichment
  18. 2026-08-12 13:50 UTCEPSS rescore
  19. 2026-08-11 13:42 UTCEPSS rescore
  20. 2026-08-11 04:08 UTCEG score recompute
  21. 2026-08-11 04:08 UTCVendor advisory
  22. 2026-08-11 04:08 UTCGHSA enrichment
  23. 2026-08-11 00:00 UTCEPSS rescore
  24. 2026-08-10 04:55 UTCEG score recompute
  25. 2026-08-10 04:55 UTCVendor advisory
  26. 2026-08-10 04:55 UTCGHSA enrichment
  27. 2026-08-09 13:46 UTCEPSS rescore
  28. 2026-08-09 05:43 UTCEG score recompute
  29. 2026-08-09 05:43 UTCVendor advisory
  30. 2026-08-09 05:43 UTCGHSA enrichment
  31. 2026-08-08 16:37 UTCEPSS rescore
  32. 2026-08-07 15:53 UTCEG score recompute
  33. 2026-08-07 15:53 UTCVendor advisory
  34. 2026-08-07 15:53 UTCGHSA enrichment
  35. 2026-08-06 13:46 UTCEPSS rescore
  36. 2026-08-06 00:40 UTCEG score recompute
  37. 2026-08-06 00:40 UTCVendor advisory
  38. 2026-08-06 00:40 UTCGHSA enrichment
  39. 2026-08-05 19:17 UTCEPSS rescore
  40. 2026-08-04 15:10 UTCEPSS rescore
  41. 2026-08-04 10:38 UTCEPSS rescore
  42. 2026-08-03 22:59 UTCEG score recompute
  43. 2026-08-03 22:59 UTCVendor advisory
  44. 2026-08-03 22:59 UTCGHSA enrichment
  45. 2026-08-03 10:35 UTCEPSS rescore
  46. 2026-08-02 15:02 UTCEG score recompute
  47. 2026-08-02 15:02 UTCVendor advisory
  48. 2026-08-02 15:02 UTCGHSA enrichment
  49. 2026-08-02 02:26 UTCEPSS rescore
  50. 2026-08-01 04:15 UTCEPSS rescore
  51. 2026-07-30 01:30 UTCEPSS rescore
  52. 2026-07-27 14:13 UTCEPSS rescore
  53. 2026-07-27 12:50 UTCEG score recompute
  54. 2026-07-27 12:50 UTCVendor advisory
  55. 2026-07-27 12:50 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-21711?
CVE-2026-21711 is a medium vulnerability published on March 30, 2026. 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…
When was CVE-2026-21711 disclosed?
CVE-2026-21711 was first published in the National Vulnerability Database on March 30, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-21711 actively exploited?
CVE-2026-21711 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.7% of all scored CVEs.
What is the CVSS score of CVE-2026-21711?
CVE-2026-21711 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-21711?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-21711, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-21711

Explore →

Is Your Infrastructure Affected by CVE-2026-21711?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs