CVE-2026-58041 is an improper resource-lifecycle flaw in Node.js node:sqlite. A StatementSyncIterator obtained through DatabaseSync#createTagStore() can remain usable after its associated cached prepared statement has been reset and rebound with new parameters. SQLTagStore invokes sqlite3_reset() directly, bypassing the StatementSync iterator-invalidation mechanism. The stale iterator can consequently continue execution against the cached statement's new binding state. Node.js 22.x, 24.x, and 26.x are affected.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Node.js vulnerability included in the Alpine nodejs-current 26.5.1-r0 security update; no technical details are provided.
A Node.js vulnerability described in the content as a SQLite write re-execution issue.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.