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**.
Metrics
Affected Vendors & Products
References
History
Tue, 11 Aug 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Stale Prepared Statement Execution After Reset in Node.js SQLite | nodejs: Node.js node:sqlite: Unintended data modification due to stale statement iterator |
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Fri, 07 Aug 2026 10:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nodejs
Nodejs nodejs |
|
| Vendors & Products |
Nodejs
Nodejs nodejs |
Tue, 04 Aug 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 04 Aug 2026 09:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Stale Prepared Statement Execution After Reset in Node.js SQLite |
Tue, 04 Aug 2026 01:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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**. | |
| Weaknesses | CWE-367 | |
| References |
| |
| Metrics |
cvssV3_0
|
Status: PUBLISHED
Assigner: hackerone
Published: 2026-08-04T00:49:58.112Z
Updated: 2026-08-04T15:04:06.975Z
Reserved: 2026-06-27T15:00:00.780Z
Link: CVE-2026-58041
Updated: 2026-08-04T14:19:43.393Z
Status : Received
Published: 2026-08-04T01:16:19.987
Modified: 2026-08-04T16:16:25.827
Link: CVE-2026-58041