nodejs · Node.js · published 2026-10-23

CVE-2026-105482

Routine No exploitation evidence; EPSS 0.5%.

CVE-2026-105482 is not known to be exploited in the wild. EPSS estimates a 0.5% chance of exploitation in the next 30 days, higher than 41% of all CVEs. This Node.js vulnerability: CVSS 7.4 (v3.0), a successful attack gives total control of the component. Fixed upstream in Node.js 26.12.1, 24.22.1, 22.23.4; patched packages are out for Red Hat Enterprise Linux; Debian and Ubuntu still have unfixed releases. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Node.js 26.12.1, 24.22.1, 22.23.4.

Linux distribution packages

If you run the distro’s package rather than an upstream build, this is the version to look for.

DistroReleasePackageStatus
Debian13 trixienodejsNo fix yet
12 bookwormnodejsNo fix yet
Ubuntu26.04 LTSnodejsNo fix yet
24.04 LTSnodejsNo fix yet
Red Hat Enterprise LinuxRHEL 10nodejs22Fixed in 22.23.4-1.el10_2 RHSA-2026:96094
RHEL 10nodejs24Fixed in 24.22.1-3.el10_2 RHSA-2026:96088
RHEL 10nodejs26Fixed in 26.12.1-3.el10_3 RHSA-2026:98619

From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.

Patch events

  1. Patch todaySecurity release

    Language runtimeNode.js

    Node.js security releases: 26.12.1, 24.22.1, 22.23.4

    Upgrade to 26.12.124.22.122.23.4

    Why: CVE-2026-111497: Known exploited server software, total technical impact.

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.5% (41th pct)FIRST EPSS v2026.06.15
CVSS base score7.4 (v3.0)
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →