# CVE-2026-106069: 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 c


- **Severity:** High 7.4 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** ALPINE-CVE-2026-106069, AZL-111047, BIT-node-2026-106069, BIT-node-min-2026-106069, DEBIAN-CVE-2026-106069, GHSA-jj44-m59q-wmrj, UBUNTU-CVE-2026-106069

## What is CVE-2026-106069?

CVE-2026-106069 is a high-severity vulnerability in nodejs node, published on 23 Oct 2026. 

### Official description

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**.

Weakness: CWE-295 (Improper Certificate Validation)

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

2 open source packages ship an affected version, including node and node-min.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node` | Bitnami | All versions | 22.23.4, 24.22.1, 26.12.1 |
| `node-min` | Bitnami | All versions | 22.23.4, 24.22.1, 26.12.1 |

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

Upgrade node to a fixed version for your release line: 22.23.4, 24.22.1 or 26.12.1.

## Is CVE-2026-106069 being exploited?

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

Public exploit code:

- Offline Node.js evidence checker for CVE-2026-106069: TLS leading-zero IPv4 resolver mismatch. Single-file Python; JSON/CSV/HTML reports; no exploit payloads. (github_poc): https://github.com/CompleteTech-Security/node-cve-2026-106069-check

## Fix prompt for AI coding agents

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

What it is: CVE-2026-106069 is a high-severity vulnerability in nodejs node, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-106069 in the wild and no public exploit code.

Affected packages and fixed versions:
- node (Bitnami): affected all versions; fixed in 22.23.4, 24.22.1, 26.12.1
- node-min (Bitnami): affected all versions; fixed in 22.23.4, 24.22.1, 26.12.1

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-106069/ (Markdown: https://insights.sbomify.com/CVE-2026-106069/index.md)
```

## Sources

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

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