CVE-2026-48930

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw in Node.js TLS hostname handling can cause Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation in resolver bindings. This vulnerability affects all supported release lines: Node.js 22, Node.js 24, and Node.js 26.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

June 26, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Aug 15, 2026
No patch confirmed yet.
generic

Node.js — Thursday, June 18, 2026 Security Releases

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

Vendor Advisories for CVE-2026-48930(12)

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

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnodejs:22-8100020260703140402.6d8804032026-07-20redhat
redhatnodejs:24-8100020260630152626.6d8804032026-07-15redhat
redhatnodejs22-1:22.23.1-2.el10_22026-07-06redhat
redhatnodejs:24-9080020260626074955.rhel92026-07-06redhat
redhatnodejs:22-9080020260626075442.rhel92026-07-06redhat
redhatnodejs24-1:24.18.0-1.el10_22026-07-06redhat
redhatnodejs22-main-22.23.1-2.hum12026-07-03redhat
redhatnodejs24-main-24.18.0-0.2.hum12026-07-01redhat
redhatnodejs26-main-26.4.0-1.3.hum12026-06-30redhat
redhatnodejs20-main-20.20.2-1.hum12026-04-21redhat
redhatnodejs25-main-25.9.0-1.1.hum12026-04-10redhat

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 8 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
nodejs—22.23.0-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
nodejs—22.23.0-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
nodejs—24.17.0-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
nodejs—24.17.0-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
nodejs12.21.0~dfsg-5 ... 24.18.0+dfsg+~cs24.13.2-1 (174 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
nodejs18.13.0+dfsg1-1 ... 24.18.0+dfsg+~cs24.13.2-1 (87 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
nodejs20.19.2+dfsg-1 ... 24.18.0+dfsg+~cs24.13.2-1 (42 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
nodejs20.19.2+dfsg-1 ... 24.16.0+dfsg+~cs24.13.1-2 (38 versions)24.17.0+dfsg+~cs24.13.2-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 76× in last 7d / 328× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 389 total refreshes for this CVE.

  1. 2026-08-21 09:05 UTCVendor advisory
  2. 2026-08-21 09:05 UTCGHSA enrichment
  3. 2026-08-21 04:59 UTCVendor advisory
  4. 2026-08-21 04:59 UTCGHSA enrichment
  5. 2026-08-21 00:15 UTCEG score recompute
  6. 2026-08-21 00:15 UTCVendor advisory
  7. 2026-08-21 00:15 UTCGHSA enrichment
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-20 20:00 UTCVendor advisory
  10. 2026-08-20 20:00 UTCGHSA enrichment
  11. 2026-08-20 15:57 UTCVendor advisory
  12. 2026-08-20 15:57 UTCGHSA enrichment
  13. 2026-08-20 11:06 UTCVendor advisory
  14. 2026-08-20 11:06 UTCGHSA enrichment
  15. 2026-08-20 06:59 UTCEG score recompute
  16. 2026-08-20 06:59 UTCVendor advisory
  17. 2026-08-20 06:59 UTCGHSA enrichment
  18. 2026-08-19 17:04 UTCEPSS rescore
  19. 2026-08-19 14:42 UTCVendor advisory
  20. 2026-08-19 14:41 UTCGHSA enrichment
  21. 2026-08-19 10:28 UTCVendor advisory
  22. 2026-08-19 10:28 UTCGHSA enrichment
  23. 2026-08-19 05:38 UTCVendor advisory
  24. 2026-08-19 05:38 UTCGHSA enrichment
  25. 2026-08-19 01:07 UTCEG score recompute
Show 75 more
  1. 2026-08-19 01:07 UTCVendor advisory
  2. 2026-08-19 01:07 UTCGHSA enrichment
  3. 2026-08-18 13:48 UTCEPSS rescore
  4. 2026-08-17 17:01 UTCEG score recompute
  5. 2026-08-17 17:01 UTCVendor advisory
  6. 2026-08-17 17:01 UTCGHSA enrichment
  7. 2026-08-17 13:47 UTCEPSS rescore
  8. 2026-08-17 12:59 UTCVendor advisory
  9. 2026-08-17 12:59 UTCGHSA enrichment
  10. 2026-08-17 08:56 UTCVendor advisory
  11. 2026-08-17 08:56 UTCGHSA enrichment
  12. 2026-08-17 04:54 UTCVendor advisory
  13. 2026-08-17 04:54 UTCGHSA enrichment
  14. 2026-08-17 00:51 UTCVendor advisory
  15. 2026-08-17 00:51 UTCGHSA enrichment
  16. 2026-08-16 20:48 UTCVendor advisory
  17. 2026-08-16 20:48 UTCGHSA enrichment
  18. 2026-08-16 16:45 UTCEG score recompute
  19. 2026-08-16 16:45 UTCVendor advisory
  20. 2026-08-16 16:45 UTCGHSA enrichment
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 12:43 UTCVendor advisory
  23. 2026-08-16 12:43 UTCGHSA enrichment
  24. 2026-08-16 08:40 UTCVendor advisory
  25. 2026-08-16 08:40 UTCGHSA enrichment
  26. 2026-08-16 04:37 UTCEG score recompute
  27. 2026-08-16 04:37 UTCVendor advisory
  28. 2026-08-16 04:37 UTCGHSA enrichment
  29. 2026-08-16 02:14 UTCEPSS rescore
  30. 2026-08-16 00:35 UTCVendor advisory
  31. 2026-08-16 00:35 UTCGHSA enrichment
  32. 2026-08-15 20:32 UTCVendor advisory
  33. 2026-08-15 20:32 UTCGHSA enrichment
  34. 2026-08-15 16:29 UTCVendor advisory
  35. 2026-08-15 16:29 UTCGHSA enrichment
  36. 2026-08-15 12:26 UTCVendor advisory
  37. 2026-08-15 12:26 UTCGHSA enrichment
  38. 2026-08-15 08:23 UTCVendor advisory
  39. 2026-08-15 08:23 UTCGHSA enrichment
  40. 2026-08-15 04:16 UTCEG score recompute
  41. 2026-08-15 04:16 UTCVendor advisory
  42. 2026-08-15 04:16 UTCGHSA enrichment
  43. 2026-08-15 01:30 UTCEPSS rescore
  44. 2026-08-15 00:13 UTCVendor advisory
  45. 2026-08-15 00:13 UTCGHSA enrichment
  46. 2026-08-14 20:11 UTCVendor advisory
  47. 2026-08-14 20:11 UTCGHSA enrichment
  48. 2026-08-14 16:08 UTCVendor advisory
  49. 2026-08-14 16:08 UTCGHSA enrichment
  50. 2026-08-14 12:06 UTCVendor advisory
  51. 2026-08-14 12:06 UTCGHSA enrichment
  52. 2026-08-14 08:04 UTCVendor advisory
  53. 2026-08-14 08:04 UTCGHSA enrichment
  54. 2026-08-14 04:01 UTCVendor advisory
  55. 2026-08-14 04:01 UTCGHSA enrichment
  56. 2026-08-13 23:59 UTCEG score recompute
  57. 2026-08-13 23:59 UTCVendor advisory
  58. 2026-08-13 23:59 UTCGHSA enrichment
  59. 2026-08-13 22:00 UTCEPSS rescore
  60. 2026-08-13 19:56 UTCVendor advisory
  61. 2026-08-13 19:56 UTCGHSA enrichment
  62. 2026-08-13 15:53 UTCVendor advisory
  63. 2026-08-13 15:53 UTCGHSA enrichment
  64. 2026-08-13 11:48 UTCVendor advisory
  65. 2026-08-13 11:48 UTCGHSA enrichment
  66. 2026-08-13 07:45 UTCVendor advisory
  67. 2026-08-13 07:45 UTCGHSA enrichment
  68. 2026-08-13 03:09 UTCVendor advisory
  69. 2026-08-13 03:09 UTCGHSA enrichment
  70. 2026-08-12 23:07 UTCVendor advisory
  71. 2026-08-12 23:07 UTCGHSA enrichment
  72. 2026-08-12 19:05 UTCVendor advisory
  73. 2026-08-12 19:05 UTCGHSA enrichment
  74. 2026-08-12 15:03 UTCEG score recompute
  75. 2026-08-12 15:03 UTCVendor advisory

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-48930?
CVE-2026-48930 is a critical vulnerability published on June 26, 2026. A flaw in Node.js TLS hostname handling can cause Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation in resolver bindings. This vulnerability affects all supported release lines: Node.js 22, Node.js 24, and Node.js 26.
When was CVE-2026-48930 disclosed?
CVE-2026-48930 was first published in the National Vulnerability Database on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48930 actively exploited?
CVE-2026-48930 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.6% of all scored CVEs.
What is the CVSS score of CVE-2026-48930?
CVE-2026-48930 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-48930?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48930, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-48930?

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

Start Free Scan →Browse All CVEs