CVE-2026-21712

A flaw in Node.js URL processing causes an assertion failure in native code when `url.format()` is called with a malformed internationalized domain name (IDN) containing invalid characters, crashing the Node.js process.

Published: 2026-03-30 Last update: 2026-05-10 Assigner: [email protected] Source: [email protected]
NVD Status：Awaiting Analysis，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-21712 is rated Low Risk (23.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.01%). 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-21712

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-03-31 — 0.01% —

Full EPSS history (1 record total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.7 3.0 MEDIUM
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
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:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.1 3.6 [email protected]

Weakness enumeration for CVE-2026-21712

GitHub Security Advisory for CVE-2026-21712

GHSA-h8r7-m85c-mjhv · Severity: medium — A flaw in Node.js URL processing causes an assertion failure in native code when `url.format()`...

OS Trackers for CVE-2026-21712

vendor priority summary link
alpine — CVE-2026-21712: 1 source package rows (nodejs); 2 state rows across 2 repos (3.23-main, edge-main); fixed 2, open 0. https://security.alpinelinux.org/vuln/CVE-2026-21712
debian unimportant CVE-2026-21712 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-21712
redhat medium — https://access.redhat.com/security/cve/CVE-2026-21712
suse medium CVE-2026-21712 severity moderate: SUSE including 68 source package names (corepack20, corepack22, …), 165 product×package rows across 21 product lines (SUSE Liberty Linux 8, SUSE Liberty Linux 9, … (21 product lines)): Known Not Affected 131, Fixed 29, First Fixed 5. https://www.suse.com/security/cve/CVE-2026-21712/
ubuntu medium CVE-2026-21712 medium priority: Ubuntu including 1 source packages (nodejs), 8 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): needs-triage 8. https://ubuntu.com/security/CVE-2026-21712

Affected software / configurations for CVE-2026-21712

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-21712

cvelogic Threat Intelligence