Quick answers
- Is CVE-2026-119591 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119591 being exploited in the wild.
- How severe is CVE-2026-119591?
- Medium severity, with a CVSS score of 5.5, published 30 October 2026.
- Which products and versions are affected?
- Sqlite before 3.54.0.
- Is there a fix for CVE-2026-119591?
- Yes: fixed in SQLite 3.54.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119591 attacked?
- It is attacked over the network or with local access, in a software library.
- Am I affected by CVE-2026-119591?
- Check whether you run Sqlite at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: SQLite 3.54.0
Technical details
The vulnerability is a stack exhaustion flaw in the countOfViewOptimization() function triggered when processing COUNT(*) queries over large multi-row VALUES clauses. Deeply nested TK_PLUS expressions are generated, and their recursive freeing in sqlite3ExprDeleteNN() exhausts the C stack. An attacker providing untrusted SQL or a crafted database file can trigger this condition; a fix exists in version 3.54.0.
Affected products
- SQLite SQLite before 3.54.0
Timeline
- 2026-10-30: disclosed
- 2026-10-30: advisory