CVE-2026-58041

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

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

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

A fix is available — apply it.

A flaw in Node.js node:sqlite allows a stale StatementSyncIterator created through DatabaseSync#createTagStore() to continue executing a cached prepared statement after it has been reset and rebound with new parameters. SQLTagStore resets cached statements using sqlite3_reset() directly, bypassing the iterator invalidation mechanism introduced for StatementSync in recent releases This vulnerability affects Node.js 22.x, 24.x, and 26.x.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
24(Track)
EG Risk 24/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
Severity53% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
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-58041(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

(6 across 6 ecosystems)
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 28× in last 7d / 60× 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-21 01:49 UTCEG score recompute
  2. 2026-08-21 01:49 UTCVendor advisory
  3. 2026-08-21 01:49 UTCGHSA enrichment
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 01:13 UTCEG score recompute
  6. 2026-08-20 01:13 UTCVendor advisory
  7. 2026-08-20 01:13 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 00:37 UTCEG score recompute
  10. 2026-08-19 00:37 UTCVendor advisory
  11. 2026-08-19 00:37 UTCGHSA enrichment
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-18 00:01 UTCEG score recompute
  14. 2026-08-18 00:01 UTCVendor advisory
  15. 2026-08-18 00:01 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-16 23:27 UTCEG score recompute
  18. 2026-08-16 23:27 UTCVendor advisory
  19. 2026-08-16 23:27 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 22:53 UTCEG score recompute
  23. 2026-08-15 22:53 UTCVendor advisory
  24. 2026-08-15 22:53 UTCGHSA enrichment
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 35 more
  1. 2026-08-14 22:19 UTCEG score recompute
  2. 2026-08-14 22:19 UTCVendor advisory
  3. 2026-08-14 22:19 UTCGHSA enrichment
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-13 21:44 UTCVendor advisory
  6. 2026-08-13 21:44 UTCGHSA enrichment
  7. 2026-08-12 21:10 UTCEG score recompute
  8. 2026-08-12 21:10 UTCVendor advisory
  9. 2026-08-12 21:10 UTCGHSA enrichment
  10. 2026-08-12 13:51 UTCEPSS rescore
  11. 2026-08-11 20:33 UTCEG score recompute
  12. 2026-08-11 20:33 UTCGHSA enrichment
  13. 2026-08-11 00:00 UTCEPSS rescore
  14. 2026-08-10 19:59 UTCGHSA enrichment
  15. 2026-08-09 19:25 UTCEG score recompute
  16. 2026-08-09 19:25 UTCGHSA enrichment
  17. 2026-08-09 13:46 UTCEPSS rescore
  18. 2026-08-08 18:51 UTCEG score recompute
  19. 2026-08-08 18:51 UTCGHSA enrichment
  20. 2026-08-08 16:37 UTCEPSS rescore
  21. 2026-08-07 18:16 UTCEG score recompute
  22. 2026-08-07 18:16 UTCGHSA enrichment
  23. 2026-08-06 17:42 UTCEG score recompute
  24. 2026-08-06 17:42 UTCGHSA enrichment
  25. 2026-08-06 13:47 UTCEPSS rescore
  26. 2026-08-05 19:17 UTCEPSS rescore
  27. 2026-08-05 17:07 UTCGHSA enrichment
  28. 2026-08-04 16:33 UTCEG score recompute
  29. 2026-08-04 16:33 UTCGHSA enrichment
  30. 2026-08-04 15:38 UTCEG score recompute
  31. 2026-08-04 15:38 UTCGHSA enrichment
  32. 2026-08-04 15:10 UTCEPSS rescore
  33. 2026-08-04 01:24 UTCEG score recompute
  34. 2026-08-04 00:59 UTCEG score recompute
  35. 2026-08-04 00:58 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-58041?
CVE-2026-58041 is a medium vulnerability published on August 4, 2026. A flaw in Node.js node:sqlite allows a stale StatementSyncIterator created through DatabaseSync#createTagStore() to continue executing a cached prepared statement after it has been reset and rebound with new parameters. SQLTagStore resets cached statements using sqlite3_reset() directly, bypassing…
When was CVE-2026-58041 disclosed?
CVE-2026-58041 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-58041 actively exploited?
CVE-2026-58041 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 75.1% of all scored CVEs.
What is the CVSS score of CVE-2026-58041?
CVE-2026-58041 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-58041?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58041, 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-58041

Explore →

Is Your Infrastructure Affected by CVE-2026-58041?

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

Start Free Scan →Browse All CVEs