NUL byte truncation of hostnames in Node.js DNS resolve functions
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- Partial Red Hat: 3 fixed, 4 without a fix
Attack profile from CVSS 3.0 · CNA. Fix status from CNA and Red Hat. Impact type from CWE-284.
Summary
Node.js 22.23.3, 24.22.0 and 26.12.0 are affected. The dns.resolve*() functions and dns.reverse() silently truncate a hostname at a NUL byte because the name is passed to c-ares as a C string (CWE-284). An application that validates a hostname and then resolves it with these functions can act on records for a different name, and an attacker who controls the input can trigger this without privileges. This is an incomplete fix of an earlier flaw (CVE-2026-48930) that covered only dns.lookup() and the net/tls host options.
Written with Claude Haiku 5.5 from the sources below · 2026-11-02
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
The sources list no fixed version for Node.js. Red Hat fixes it in Red Hat Enterprise Linux AppStream 8 and 9 through RHSA-2026:92376 and RHSA-2026:92378, and in Red Hat Hardened Images through RHSA-2026:87702 and RHSA-2026:87703. Red Hat has no fix available for Red Hat Enterprise Linux 8, 9 and 10.
Written with Claude Haiku 5.5 from the sources below · 2026-11-02
Red Hat 4 advisories
- RHSA-2026:92378 Released 2026-10-29 · Red Hat rating Importantnodejs:24 security, bug fix, and enhancement update
- Red Hat Enterprise Linux AppStream (v. 9) nodejs-1:24.22.1-3.module+el9.8.0+25216+afa2a4a4.aarch64::nodejs:24, nodejs-1:24.22.1-3.module+el9.8.0+25216+afa2a4a4.ppc64le::nodejs:24, nodejs-1:24.22.1-3.module+el9.8.0+25216+afa2a4a4.s390x::nodejs:24 +25
- RHSA-2026:92376 Released 2026-10-29 · Red Hat rating Importantnodejs:24 security, bug fix, and enhancement update
- Red Hat Enterprise Linux AppStream (v. 8) nodejs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.aarch64::nodejs:24, nodejs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.ppc64le::nodejs:24, nodejs-1:24.22.1-1.module+el8.10.0+25218+d9e131cb.s390x::nodejs:24 +25
- RHSA-2026:87703 Released 2026-10-22 · Red Hat rating ImportantRed Hat Hardened Images RPMs bug fix and enhancement update
- Red Hat Hardened Images nodejs26-1:26.12.1-0.1.hum1@aarch64, nodejs26-1:26.12.1-0.1.hum1@s390x, nodejs26-1:26.12.1-0.1.hum1@src +22
Show 1 more Red Hat advisories
- RHSA-2026:87702 Released 2026-10-22 · Red Hat rating ImportantRed Hat Hardened Images RPMs bug fix and enhancement update
- Red Hat Hardened Images nodejs22-1:22.23.4-2.3.2.3.hum1@aarch64, nodejs22-1:22.23.4-2.3.2.3.hum1@s390x, nodejs22-1:22.23.4-2.3.2.3.hum1@src +22
Vendor assessments
Red Hat
Red Hat rating: Important. Red Hat's page for this CVE →
| Product | Status | Plan or fix |
|---|---|---|
| Red Hat Enterprise Linux 10 | Affected | No fix yet |
| Red Hat Enterprise Linux 8 | Affected | No fix yet |
| Red Hat Enterprise Linux 9 | Affected | No fix yet |
| Red Hat Hardened Images | Affected | No fix planned: Will not fix |
| Red Hat Enterprise Linux AppStream (v. 8) | Fixed | RHSA-2026:92376 |
| Red Hat Enterprise Linux AppStream (v. 9) | Fixed | RHSA-2026:92378 |
| Red Hat Hardened Images | Fixed | RHSA-2026:87702, RHSA-2026:87703 |
Not affected: 1 product
- Red Hat Hardened Images
Timeline
- 2026-10-23 Threatist record created from CVE-2026-105482
- 2026-10-24 Priority changed: MEDIUM → LOW
- 2026-10-24 Affected versions changed · Red Hat
- 2026-10-24 CVSS score added · Red Hat
- 2026-10-29 Fix available: RHSA-2026:87703 · Red Hat
- 2026-10-29 Fix available: Red Hat Hardened Images · Red Hat
- 2026-10-30 Fix available: RHSA-2026:87702 · Red Hat
- 2026-10-30 Fix available: RHSA-2026:92378 · Red Hat
- 2026-10-30 Fix available: RHSA-2026:92376 · Red Hat
- 2026-10-30 Fix available: Red Hat Enterprise Linux AppStream (v. 8), Red Hat Enterprise Linux AppStream (v. 9) · Red Hat
- 2026-10-30 Affected versions changed · Red Hat
- 2026-11-02 CISA SSVC decision points changed
More NodeJS vulnerabilities
- TI-2026-79288 Out-of-bounds write in Google Brotli decoder KEVCVSS 4.0CRITICAL 9.2
- TI-2023-23979 The HTTP/2 protocol allows a denial of service (server resource consumption) because… KEVCVSS 3.1HIGH 7.5
- TI-2024-18584 Race condition in NodeJS Node CVSS 3.0HIGH 8.2
- TI-2016-01993 The DES and Triple DES ciphers, as used in the TLS, SSH, and IPSec protocols and other… CVSS 3.1HIGH 7.5
- TI-2024-03325 Command injection vulnerability in programing languages on Microsoft Windows operating system. CVSS 3.1CRITICAL 9.8
- TI-2022-03472 X.509 Email Address Variable Length Buffer Overflow CVSS 3.1HIGH 7.5
Sources
- CVE-2026-105482 · CVE Program
- CVE-2026-105482 · NVD
- FIRST EPSS
- CVE-2026-105482 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences