Описание
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.
A flaw was found in Node.js's node:sqlite module. This vulnerability allows a previously used database statement, which should have been reset, to be re-executed with new parameters. This could lead to unintended data modifications or integrity issues within the application.
Отчет
This flaw strictly impacts data Integrity with zero effect on Confidentiality or Availability (C:N, I:H, A:N). Practical exploitation occurs when an application utilizes the experimental node:sqlite SQL tag store feature while managing statement iterators. Under these high-complexity conditions (AC:H) requiring specific user-driven interaction sequences (UI:R), a stale iterator can execute a reset statement with new parameters, leading to unintended database writes. Applications that do not use node:sqlite tag stores or statement iterators are completely unaffected. Red Hat and upstream CVSS scores align at 5.3 (Moderate) due to these strict operational constraints.
Меры по смягчению последствий
Applications using Node.js that leverage the experimental node:sqlite SQL tag store feature should avoid using DatabaseSync#createTagStore() and StatementSyncIterator to prevent unintended data modification. If this feature is not essential, refactoring the application to remove its usage will mitigate the vulnerability.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat Enterprise Linux 10 | nodejs22 | Not affected | ||
| Red Hat Enterprise Linux 8 | nodejs:22/nodejs | Not affected | ||
| Red Hat Enterprise Linux 9 | nodejs:22/nodejs | Not affected | ||
| Red Hat Enterprise Linux 10 | nodejs24 | Fixed | RHSA-2026:61377 | 31.08.2026 |
| Red Hat Enterprise Linux 10 | nodejs26 | Fixed | RHSA-2026:98619 | 11.11.2026 |
| Red Hat Enterprise Linux 8 | nodejs | Fixed | RHSA-2026:62583 | 02.09.2026 |
| Red Hat Enterprise Linux 9 | nodejs | Fixed | RHSA-2026:61386 | 31.08.2026 |
| Red Hat Enterprise Linux 9 | nodejs | Fixed | RHSA-2026:97855 | 10.11.2026 |
| Red Hat Hardened Images | nodejs22-main-10.9.8-1.22.23.2.2.3.hum1 | Fixed | RHSA-2026:48305 | 29.07.2026 |
| Red Hat Hardened Images | nodejs22-main-22.23.2-2.3.hum1 | Fixed | RHSA-2026:48305 | 29.07.2026 |
Показывать по
Дополнительная информация
Статус:
EPSS
5.3 Medium
CVSS3
Связанные уязвимости
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**.
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**.
A flaw in Node.js node:sqlite allows a stale StatementSyncIterator cre ...
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**.
EPSS
5.3 Medium
CVSS3