CVE-2026-58045

MEDIUMPre-NVD 6.26.2—
EchelonGraph scoreHIGH confidence

Score 6.2 from GitHub Security Advisory published 2026-08-04. a secondary CVSS source baseline 6.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
6.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.2Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw in Node.js allows a spoofed TypedArray byteLength to trigger a reachable assertion in the synchronous node:zlib APIs, causing the entire process to crash. All 11 synchronous zlib functions are affected. Repeated exploitation of this condition can result in a denial of service. This vulnerability affects Node.js 22.x, 24.x, and 26.x.

CVSS v3
6.2
EG Score
6.2(high)
EG Risk
28(Track)
EG Risk 28/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
Severity62% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

August 4, 2026

Last Modified

August 4, 2026

Advisory Details (1)

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

Node.js — Wednesday, July 29, 2026 Security Releases

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

Vendor Advisories for CVE-2026-58045(4)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnodejs26-main-26.7.0-1.5.1.hum12026-08-10redhat
redhatnodejs24-main-24.18.1-0.1.hum12026-07-30redhat
redhatnodejs22-main-22.23.2-2.3.hum12026-07-29redhat

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.2-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
nodejs—22.23.2-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
nodejs—24.18.1-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
nodejs—24.18.1-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.18.0+dfsg+~cs24.13.2-1 (40 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 26× in last 7d / 61× 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.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 12:17 UTCEG score recompute
  3. 2026-08-20 12:17 UTCVendor advisory
  4. 2026-08-20 12:17 UTCGHSA enrichment
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-19 14:03 UTCVendor advisory
  7. 2026-08-19 14:03 UTCGHSA enrichment
  8. 2026-08-18 15:48 UTCEG score recompute
  9. 2026-08-18 15:48 UTCVendor advisory
  10. 2026-08-18 15:48 UTCGHSA enrichment
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-17 15:54 UTCEG score recompute
  13. 2026-08-17 15:54 UTCVendor advisory
  14. 2026-08-17 15:54 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-16 17:40 UTCEG score recompute
  17. 2026-08-16 17:40 UTCVendor advisory
  18. 2026-08-16 17:40 UTCGHSA enrichment
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 19:19 UTCEG score recompute
  22. 2026-08-15 19:19 UTCVendor advisory
  23. 2026-08-15 19:19 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 21:05 UTCVendor advisory
Show 36 more
  1. 2026-08-14 21:05 UTCGHSA enrichment
  2. 2026-08-13 22:51 UTCEG score recompute
  3. 2026-08-13 22:51 UTCVendor advisory
  4. 2026-08-13 22:51 UTCGHSA enrichment
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-13 00:37 UTCEG score recompute
  7. 2026-08-13 00:37 UTCVendor advisory
  8. 2026-08-13 00:37 UTCGHSA enrichment
  9. 2026-08-12 13:51 UTCEPSS rescore
  10. 2026-08-12 02:23 UTCEG score recompute
  11. 2026-08-12 02:23 UTCVendor advisory
  12. 2026-08-12 02:23 UTCGHSA enrichment
  13. 2026-08-11 04:10 UTCEG score recompute
  14. 2026-08-11 04:09 UTCGHSA enrichment
  15. 2026-08-11 00:00 UTCEPSS rescore
  16. 2026-08-10 05:56 UTCEG score recompute
  17. 2026-08-10 05:56 UTCGHSA enrichment
  18. 2026-08-09 13:46 UTCEPSS rescore
  19. 2026-08-09 07:42 UTCGHSA enrichment
  20. 2026-08-08 09:29 UTCEG score recompute
  21. 2026-08-08 09:29 UTCGHSA enrichment
  22. 2026-08-07 11:15 UTCEG score recompute
  23. 2026-08-07 11:15 UTCGHSA enrichment
  24. 2026-08-06 13:47 UTCEPSS rescore
  25. 2026-08-06 13:01 UTCEG score recompute
  26. 2026-08-06 13:01 UTCGHSA enrichment
  27. 2026-08-05 19:17 UTCEPSS rescore
  28. 2026-08-05 14:47 UTCGHSA enrichment
  29. 2026-08-04 16:33 UTCEG score recompute
  30. 2026-08-04 16:33 UTCGHSA enrichment
  31. 2026-08-04 15:38 UTCEG score recompute
  32. 2026-08-04 15:38 UTCGHSA enrichment
  33. 2026-08-04 15:10 UTCEPSS rescore
  34. 2026-08-04 01:24 UTCEG score recompute
  35. 2026-08-04 00:59 UTCEG score recompute
  36. 2026-08-04 00:58 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-58045?
CVE-2026-58045 is a medium vulnerability published on August 4, 2026. A flaw in Node.js allows a spoofed TypedArray byteLength to trigger a reachable assertion in the synchronous node:zlib APIs, causing the entire process to crash. All 11 synchronous zlib functions are affected. Repeated exploitation of this condition can result in a denial of service. This…
When was CVE-2026-58045 disclosed?
CVE-2026-58045 was first published in the National Vulnerability Database on August 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58045 actively exploited?
CVE-2026-58045 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 90.0% of all scored CVEs.
What is the CVSS score of CVE-2026-58045?
CVE-2026-58045 has a CVSS v3 base score of 6.2 (NVD).
How do I remediate CVE-2026-58045?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58045, 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-58045

Explore →

Is Your Infrastructure Affected by CVE-2026-58045?

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

Start Free Scan →Browse All CVEs