Improper Neutralization of Null Byte or NUL Character Affecting nodejs22-libs package, versions <1:22.23.4-1.amzn2023.0.1


Severity

Recommended
0.0
high
0
10

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.42% (37th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-AMZN2023-NODEJS22LIBS-21706240
  • published25 Oct 2026
  • disclosed23 Oct 2026

Introduced: 23 Oct 2026

NewCVE-2026-105482  (opens in a new tab)
CWE-158  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2023 nodejs22-libs to version 1:22.23.4-1.amzn2023.0.1 or higher.
This issue was patched in ALAS2023-2026-3328.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs22-libs package and not the nodejs22-libs package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2023 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1