CVE-2026-58041

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM 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(medium)
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
17%
KEV
Not listed

Published

August 4, 2026

Last Modified

September 3, 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.20.0+dfsg+~cs24.13.3-2 (45 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
nodejs20.19.2+dfsg-1 ... 24.18.0+dfsg+~cs24.13.2-1 (40 versions)24.19.0+dfsg+~cs24.13.3-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 101× 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 157 total refreshes for this CVE.

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

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, with the most recent update on September 3, 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 82.8% 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