# CVE-2026-119372: SQLite use-after-free in fts3BestSnippet()

Source: https://junglewise.ai/threats/cve-2026-119372-sqlite-before-3-54-0-built-with-fts3-fts4-and-sqlite-enable-fts3  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-30. Updated: 2026-10-30  
License: CC BY 4.0 with a link back

CVE-2026-119372 · Severity: medium · CVSS 5.5 · Published 2026-10-30

SQLite is a widely-used embedded database engine built into mobile phones, computers, and countless applications. A use-after-free vulnerability in the full-text search component allows attackers to read freed memory and crash applications by crafting specially-formed database queries combining text search operators. This affects any application using SQLite with full-text search enabled.

Technologies: [Sqlite](https://junglewise.ai/threats/technologies/sqlite-sqlite). Vendors: [SQLite](https://junglewise.ai/threats/vendors/sqlite).

## Quick answers

**Is CVE-2026-119372 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-119372 being exploited in the wild.

**How severe is CVE-2026-119372?** 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-119372?** 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-119372 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-119372?** 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

A use-after-free vulnerability exists in fts3BestSnippet() when SQLite is built with FTS3/FTS4 and SQLITE_ENABLE_FTS3_PARENTHESIS enabled. Attackers trigger the bug by executing a full-text MATCH query combining OR and NEAR operators with the snippet() function, causing the code to reference dangling cached position-list pointers. Successful exploitation results in heap memory disclosure or process crash.

## Affected products

- SQLite SQLite before 3.54.0

## Timeline

- 2026-10-30: disclosed

## References

- [https://sqlite.org/](https://sqlite.org/)
- [https://abraxaslabs.tech/research/sqlite-fts3-snippet](https://abraxaslabs.tech/research/sqlite-fts3-snippet)

## Related threats

- [SQLite stack exhaustion in countOfViewOptimization](https://junglewise.ai/threats/cve-2026-119591-sqlite-before-3-54-0-contains-a-stack-exhaustion-vulnerability)
- [SQLite heap buffer overflow in session extension](https://junglewise.ai/threats/cve-2026-119379-sqlite-before-3-54-0-built-with-the-session-extension-contains-a)
- [SQLite use-after-free in R-Tree extension](https://junglewise.ai/threats/cve-2026-119378-sqlite-before-3-54-0-contains-a-use-after-free-vulnerability-in)
- [SQLite information disclosure via undersized WAL page cache](https://junglewise.ai/threats/cve-2026-119375-sqlite-before-3-54-0-contains-an-information-disclosure)
- [SQLite heap buffer overflow in FTS5 secure delete](https://junglewise.ai/threats/cve-2026-119374-sqlite-before-3-54-0-built-with-fts5-contains-a-heap-buffer)
