CVE-2026-21711MediumMicrosoft CVSS 5.3CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Microsoft advisory for CVE-2026-21711 — azl3 nodejs24

Published
May 31, 2026
Last Modified
—

🔗 CVE IDs covered (1)

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21711. This page also shows what EchelonGraph holds for CVE-2026-21711, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products3

  • azl3 nodejs24 24.13.0-3 on Azure Linux 3.0
  • azl3 nodejs24 24.14.1-1 on Azure Linux 3.0
  • azl3 nodejs24 24.14.1-2 on Azure Linux 3.0

🧭 EchelonGraph on CVE-2026-21711

EchelonGraph score
5.3 MEDIUM
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

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 by HackerOne, the CVE Numbering Authority that assigned CVE-2026-21711, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (1)