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

DEBIAN-CVE-2026-106069, 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-106069
- Platform: Linux
- Released: Nov 11, 2026
- Priority: High (Closes CVE-2026-106069, high severity)
- CVEs: 1, exploited: 0, on CISA KEV: 0
- Vendor advisory: https://security-tracker.debian.org/tracker/CVE-2026-106069

## 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-106069](https://patchblox.com/security/data/cve/CVE-2026-106069.md) | High | A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP address than the one the client connected to, when the host is a non-canonical IPv4 literal with a leading zero, such as `0127.0.0.1`.  `tls.checkServerIdentity()` normalizes the host following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address.  This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**. | 8.1 | 0.0030 |  |

---

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.