CVE-2026-105482

HIGHPre-NVD 7.47.4
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-10-23. A secondary CVSS source baseline 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-109105 (ENISA EUVD) · GHSA-4qmx-59c6-fr6r (GitHub Security Advisories)Source: ENISA EUVD

7.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.4Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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 v3
7.4
EG Score
7.4HIGHhigh confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity74% × 45%
Impact severity (EG Severity): CVSS 7.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.4): severity, escalated by confirmed exploitation. This CVE's 7.4 is its impact severity (EG Severity), not escalated.

EG Severity
7.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-08). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 23, 2026

Last Modified

November 2, 2026

Advisory Details (1)

Auto-updated Oct 23, 2026
Patch available.
Web page

Node.js — Wednesday, October 21, 2026 Security Releases

https://nodejs.org/en/blog/vulnerability/october-2026-security-releases

Vendor Advisories for CVE-2026-105482(11)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatnodejs:24-8100020261027151919.6d8804032026-10-29redhat
redhatnodejs:24-9080020261027142403.rhel92026-10-29redhat
redhatnodejs26-main-26.12.1-0.1.hum12026-10-22redhat
redhatnodejs22-main-22.23.4-2.3.2.3.hum12026-10-22redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(8 across 7 ecosystems)
Alpine:v3.24(2)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 24.22.1-r0: fixed in 24.22.1-r0
—
nodejs-current—
  • every version up to 26.12.1-r0: fixed in 26.12.1-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 22.23.4-r0: fixed in 22.23.4-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 22.23.4-r0: fixed in 22.23.4-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 24.22.1-r0: fixed in 24.22.1-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs18.13.0+dfsg1-1 ... 24.22.2+dfsg+~cs24.19.2-1 (96 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs20.19.2+dfsg-1 ... 24.22.2+dfsg+~cs24.19.2-1 (51 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs20.19.2+dfsg-1 ... 24.22.0+dfsg+~cs24.19.2-2 (46 versions)
  • every version up to 24.22.1+dfsg+~cs24.19.2-1: fixed in 24.22.1+dfsg+~cs24.19.2-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  3. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  4. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-11-09 11:18 UTCEchelonGraph re-scored
  6. 2026-11-09 11:18 UTCVendor advisory
  7. 2026-11-09 11:18 UTCGHSA enrichmentGHSA-4qmx-59c6-fr6r · GitHub severity HIGH · GitHub CVSS 7.4
  8. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  10. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  12. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  15. 2026-11-02 16:27 UTCEchelonGraph re-scored
  16. 2026-11-02 16:27 UTCVendor advisory
  17. 2026-11-02 16:27 UTCGHSA enrichmentGHSA-4qmx-59c6-fr6r · GitHub severity HIGH · GitHub CVSS 7.4
  18. 2026-11-02 15:58 UTCEchelonGraph re-scored
  19. 2026-11-02 15:58 UTCVendor advisory
  20. 2026-11-02 15:57 UTCGHSA enrichmentGHSA-4qmx-59c6-fr6r · GitHub severity HIGH · GitHub CVSS 7.4
  21. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  24. 2026-10-30 14:38 UTCEchelonGraph re-scored
  25. 2026-10-30 14:38 UTCVendor advisory
Show 14 more
  1. 2026-10-30 14:38 UTCGHSA enrichmentGHSA-4qmx-59c6-fr6r · GitHub severity HIGH · GitHub CVSS 7.4
  2. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  3. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  4. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  5. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  6. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  7. 2026-10-25 14:55 UTCEchelonGraph re-scored
  8. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  9. 2026-10-23 19:47 UTCEchelonGraph re-scored
  10. 2026-10-23 19:47 UTCGHSA enrichmentGHSA-4qmx-59c6-fr6r · GitHub severity HIGH · GitHub CVSS 7.4
  11. 2026-10-23 17:26 UTCEchelonGraph re-scored
  12. 2026-10-23 16:27 UTCEchelonGraph re-scored
  13. 2026-10-23 16:21 UTCEchelonGraph re-scoredFirst assessed: 7.4 HIGH
  14. 2026-10-23 16:19 UTCMITRE cvelistV5first tracked

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCCaterMaoZi/CVE-2026-105482-POC
    Published Oct 21, 2026

    Nodejs漏洞 CVE-2026-105482 POC

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-105482?
CVE-2026-105482 is a high-severity vulnerability; its CVE record was published on October 23, 2026. 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…
When was the CVE record for CVE-2026-105482 published?
The CVE record for CVE-2026-105482 was published on October 23, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 2, 2026; the record at its source may have been updated since.
Is CVE-2026-105482 actively exploited?
CVE-2026-105482 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-105482?
CVE-2026-105482 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-105482?
A fix for CVE-2026-105482 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-105482 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-105482

Explore →

Is Your Infrastructure Affected by CVE-2026-105482?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs