CVE-2026-48934

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

Score 4.3 from GitHub Security Advisory published 2026-06-26. a secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw in Node.js TLS host verification can cause an attacker to bypass certification validation. This vulnerability affects all supported release lines: Node.js 22, Node.js 24, and Node.js 26.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
19
EG Risk 19/100

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
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.3%
EPSS %ILE
15th
KEV
Not listed

Published

June 26, 2026

Last Modified

June 29, 2026

Advisory Details (1)

Auto-updated Jun 26, 2026
Patch available.
generic

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

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

Vendor Advisories for CVE-2026-48934(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 / EcosystemFix (by version range) / PatchReleasedSource
redhatnodejs:22-8100020260703140402.6d8804032026-07-20redhat
redhatnodejs:24-8100020260630152626.6d8804032026-07-15redhat
redhatnodejs:24-9080020260626074955.rhel92026-07-06redhat
redhatnodejs:22-9080020260626075442.rhel92026-07-06redhat
redhatnodejs24-1:24.18.0-1.el10_22026-07-06redhat
redhatnodejs22-1:22.23.1-2.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 rangeFix by version rangeDependents
nodejs—
  • every version up to 22.23.0-r0: fixed in 22.23.0-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 22.23.0-r0: fixed in 22.23.0-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 24.17.0-r0: fixed in 24.17.0-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 24.17.0-r0: fixed in 24.17.0-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs12.21.0~dfsg-5 ... 24.18.0+dfsg+~cs24.13.2-1 (174 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs18.13.0+dfsg1-1 ... 18.20.4+dfsg-1~deb12u2 (22 versions)
  • every version up to 18.20.4+dfsg-1~deb12u3: fixed in 18.20.4+dfsg-1~deb12u3
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs20.19.2+dfsg-1, 20.19.2+dfsg-1+deb13u1, 20.19.2+dfsg-1+deb13u2
  • every version up to 20.19.2+dfsg-1+deb13u3: fixed in 20.19.2+dfsg-1+deb13u3
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs20.19.2+dfsg-1 ... 24.16.0+dfsg+~cs24.13.1-2 (38 versions)
  • every version up to 24.17.0+dfsg+~cs24.13.2-1: fixed in 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 4× in last 7d / 31× 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 223 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-48934?
CVE-2026-48934 is a medium vulnerability published on June 26, 2026. A flaw in Node.js TLS host verification can cause an attacker to bypass certification validation. This vulnerability affects all supported release lines: Node.js 22, Node.js 24, and Node.js 26.
When was CVE-2026-48934 disclosed?
CVE-2026-48934 was first published on June 26, 2026, with the most recent update on June 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48934 actively exploited?
CVE-2026-48934 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48934?
CVE-2026-48934 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48934?
A fix for CVE-2026-48934 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48934 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-48934

Explore →

Is Your Infrastructure Affected by CVE-2026-48934?

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

Book a Demo →Browse All CVEs