# CVE-2026-105482: A flaw in Node.js DNS resolution allows hostnames containing a NUL byte to be silently truncated by the dns.resolve*() functions and dns.reverse().


- **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-105482, AZL-111035, BIT-node-2026-105482, BIT-node-min-2026-105482, DEBIAN-CVE-2026-105482, GHSA-4qmx-59c6-fr6r, UBUNTU-CVE-2026-105482

## What is CVE-2026-105482?

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

### Official description

A flaw in Node.js DNS resolution allows hostnames containing a NUL byte to be silently truncated by the dns.resolve*() functions and dns.reverse(). This is an incomplete fix of CVE-2026-48930, which only covered dns.lookup() and the net/tls host options.

Because the name is passed to c-ares as a C string, resolving attacker.example\0.trusted.example queries attacker.example and returns its records without any error. Applications that validate a hostname, for example against a domain allowlist, and then resolve it with dns.resolve*() can act on records for a different name than the one they validated.

This vulnerability affects Node.js 26.x, 24.x, and 22.x.

Weakness: CWE-284 (Improper Access Control)

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

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-105482?

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

## Is CVE-2026-105482 being exploited?

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

Public exploit code:

- Nodejs漏洞 CVE-2026-105482 POC (github_poc): https://github.com/CaterMaoZi/CVE-2026-105482-POC
- Offline Node.js evidence checker for CVE-2026-105482: DNS resolution NUL-name truncation. Single-file Python; JSON/CSV/HTML reports; no exploit payloads. (github_poc): https://github.com/CompleteTech-Security/node-cve-2026-105482-check
- CVE-2026-105482漏洞复现 (github_poc): https://github.com/EthanTech-Offical/CVE-2026-105482-Reproduce

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105482 is a high-severity vulnerability in nodejs node, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-105482 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-105482/ (Markdown: https://insights.sbomify.com/CVE-2026-105482/index.md)
```

## Sources

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

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