CVE-2026-58041
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 w
CVSS
5.3MediumExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.29%Chance of exploitation activity in the next 30 days, higher than 20% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed inNone listedNo source names a fixed version. Check the vendor advisory below
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
Timeline
- 4 Aug 2026, 00:49 UTCPublishedCVE List
- 23 Oct 2026, 23:44 UTCExploit code publicGitHub proof-of-concept repositories
Reports 2
1 outlet mention it. Reports are not confirmation; each links to its source.
- completetech-security/node-cve-2026-58041-check: Standalone defensive checker project for CVE-2026-58041: Node.js: SQLite cached iterator write replay. One exploit per repository; implementation pending.GitHub proof-of-concept repositories, 23 Oct 2026Exploit code
- CompleteTech-LLC/node-cve-2026-58041-check: Standalone defensive checker project for CVE-2026-58041: Node.js: SQLite cached iterator write replay. One exploit per repository; implementation pending.GitHub proof-of-concept repositories, 23 Oct 2026Exploit code
Description
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.
Text from CVE List
Affected versions 3
- nodeaffected: 22.23.1 through 22.23.1CVE List
- nodeaffected: 24.18.0 through 24.18.0CVE List
- nodeaffected: 26.5.0 through 26.5.0CVE List