# CVE-2026-21712: Denial of service in node

> An attacker can crash the Node.js process by calling url.format() with a malformed internationalized domain name, causing a denial of service.

- **Severity:** Medium 5.7 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 30 Mar 2026
- **Updated:** 10 May 2026
- **Also known as:** ALPINE-CVE-2026-21712, AZL-81101, BELL-CVE-2026-21712, BIT-node-2026-21712, BIT-node-min-2026-21712, GHSA-h8r7-m85c-mjhv, MINI-86c5-mgmp-5m9w, MINI-99px-rrfc-2r47, UBUNTU-CVE-2026-21712

## What is CVE-2026-21712?

CVE-2026-21712 is a medium-severity denial of service vulnerability in Nodejs Node.js, published on 30 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-21712?

2 open source packages ship an affected version, including node and node-min. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node` | Bitnami | From 24.0.0 | 24.14.1, 25.8.2 |
| `node-min` | Bitnami | From 24.0.0 | 24.14.1, 25.8.2 |

Products: Nodejs Node.js.

## How do I fix CVE-2026-21712?

Upgrade node to a fixed version for your release line: 24.14.1 or 25.8.2.

## Is CVE-2026-21712 being exploited?

There is no known exploitation of CVE-2026-21712 in the wild and no public exploit code.

## Other vulnerabilities in Nodejs Node.js

- [CVE-2023-32002](https://insights.sbomify.com/CVE-2023-32002/): Security feature bypass in Node (critical 9.8)
- [CVE-2016-6303](https://insights.sbomify.com/CVE-2016-6303/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-15896](https://insights.sbomify.com/CVE-2017-15896/): Security feature bypass in Node.js (critical 9.1)
- [CVE-2018-7160](https://insights.sbomify.com/CVE-2018-7160/): Server-side request forgery in Node.js (high 8.8)
- [CVE-2018-12120](https://insights.sbomify.com/CVE-2018-12120/): Misconfiguration in Node.js (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-21712 and fix it if it is affected.

What it is: CVE-2026-21712 is a medium-severity denial of service vulnerability in Nodejs Node.js, published on 30 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-21712 in the wild and no public exploit code.

Affected packages and fixed versions:
- node (Bitnami): affected from 24.0.0; fixed in 24.14.1, 25.8.2
- node-min (Bitnami): affected from 24.0.0; fixed in 24.14.1, 25.8.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-21712/ (Markdown: https://insights.sbomify.com/CVE-2026-21712/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-21712
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-21712
- OSV: https://osv.dev/vulnerability/CVE-2026-21712

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-21712/
Summaries are generated and may contain mistakes; the official description above is the record.