# CVE-2026-105483: A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 a


- **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-105483, AZL-111038, BIT-node-2026-105483, BIT-node-min-2026-105483, DEBIAN-CVE-2026-105483, GHSA-8h4p-qpcq-gq24, UBUNTU-CVE-2026-105483

## What is CVE-2026-105483?

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

### Official description

A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits (`１２７.0.0.1`).

`tls.checkServerIdentity()` did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing `DNS:127.0.0.1` or `DNS:*.0.0.1` could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618.

This vulnerability affects Node.js **26.x** and **24.x**.

Weakness: CWE-295 (Improper Certificate Validation)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node` | Bitnami | From 23.0.0 | 24.22.1, 26.12.1 |
| `node-min` | Bitnami | From 23.0.0 | 24.22.1, 26.12.1 |

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

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

## Is CVE-2026-105483 being exploited?

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

Public exploit code:

- Offline Node.js evidence checker for CVE-2026-105483: TLS fullwidth-IP hostname validation bypass. Single-file Python; JSON/CSV/HTML reports; no exploit payloads. (github_poc): https://github.com/CompleteTech-Security/node-cve-2026-105483-check

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- node (Bitnami): affected from 23.0.0; fixed in 24.22.1, 26.12.1
- node-min (Bitnami): affected from 23.0.0; fixed in 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-105483/ (Markdown: https://insights.sbomify.com/CVE-2026-105483/index.md)
```

## Sources

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

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