# DEBIAN-CVE-2026-106072: nodejs security update

DEBIAN-CVE-2026-106072, released November 11, 2026, fixes 1 CVE in nodejs (version 24.22.1+dfsg+~cs24.19.2-1). None of them is reported as exploited. Patch Radar priority: High.

- Web page: https://patchblox.com/security/fix/linux/debian-cve-2026-106072
- Platform: Linux
- Released: Nov 11, 2026
- Priority: High (Closes CVE-2026-106072, high severity)
- CVEs: 1, exploited: 0, on CISA KEV: 0
- Vendor advisory: https://security-tracker.debian.org/tracker/CVE-2026-106072

## Applies to

| Product | Release | Fixed in |
|---|---|---|
| [nodejs](https://patchblox.com/security/data/product/linux/nodejs.md) | Debian 14 | 24.22.1+dfsg+~cs24.19.2-1 |

## CVEs this fix closes

| CVE | Priority | Title | CVSS | EPSS | Exploitation |
|---|---|---|---:|---:|---|
| [CVE-2026-106072](https://patchblox.com/security/data/cve/CVE-2026-106072.md) | High | A flaw in Node.js TLS hostname verification allows a certificate with only a DNS SAN to authenticate an IP endpoint when the client connects using a non-canonical IPv4 spelling, such as `0177.0.0.1`, `0x7f.0.0.1`, `2130706433` or `127.1`.  `tls.checkServerIdentity()` did not classify these hosts as IP addresses, but normalized them to their canonical form and matched the result against the certificate DNS names. A certificate containing `DNS:127.0.0.1` and no `IP Address:127.0.0.1` SAN was therefore accepted, while the same certificate is correctly rejected for `127.0.0.1`. Exploitation requires a certificate with a numeric DNS SAN issued by a CA trusted by the client, and a platform resolver that accepts these spellings, such as glibc.  This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. | 8.1 | 0.0062 |  |

---

Data as of 2026-11-11T07:45:43Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.