CVE-2026-105482 Affecting nodejs:24/nodejs-full-i18n package, versions <1:24.22.1-1.module_el8.10.0+4331+0683c9c1


Severity

Recommended
high

Based on AlmaLinux security rating.

Threat Intelligence

EPSS
0.47% (41st 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-ALMALINUX8-NODEJS-21872573
  • published30 Oct 2026
  • disclosed29 Oct 2026

Introduced: 29 Oct 2026

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

How to fix?

Upgrade AlmaLinux:8 nodejs:24/nodejs-full-i18n to version 1:24.22.1-1.module_el8.10.0+4331+0683c9c1 or higher.
This issue was patched in ALSA-2026:92376.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs:24/nodejs-full-i18n package and not the nodejs:24/nodejs-full-i18n package as distributed by AlmaLinux. See How to fix? for AlmaLinux:8 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