Vulnerability in Node.js node:sqlite (CVE-2026-58041)
Summary
Vulnerability in Node.js node:sqlite (CVE-2026-58041). Data can be tampered with by attackers.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-58041 has been found in Node.js node:sqlite.
Data can be tampered with by attackers. CVSS score: 5.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Node.js node:sqlite CVE-2026-58041" on the vendor's site.
CVE-2026-58041 (Node.js node:sqlite) — CWE-367 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-367) exists in Node.js node:sqlite.
Check the vendor advisory for the affected versions of Node.js node:sqlite.
Severity: Medium (CVSS 5.3/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Node.js node:sqlite を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Alpine Linux ALPINE-CVE-2026-58041 nodejs Fixed in: 24.18.1-r0
- BellSoft Alpaquita BELL-CVE-2026-58041 nodejs Fixed in: 24.18.1-r0
- Debian DEBIAN-CVE-2026-58041 nodejs Fixed in: 24.19.0+dfsg+~cs24.13.3-1
- Ubuntu UBUNTU-CVE-2026-58041 nodejs
References
- web nodejs.org
- web nvd.nist.gov
- web github.com