SQLite before 3.54.0 Heap Buffer Overflow via FTS5 fts5DoSecureDelete()
Affects SQLite versions before 3.54.0 when the FTS5 secure-delete path runs on a strategically corrupted database with an FTS5 index. Fixed in 3.54.0.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 3.54.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
SQLite, the embedded database library used by many applications, is affected when built with the FTS5 full-text search extension. Opening a crafted database with a corrupted FTS5 index and performing deletes with secure-delete enabled can corrupt heap memory, potentially crashing the application.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
SQLite before 3.54.0 built with FTS5 contains a heap buffer overflow in fts5DoSecureDelete() that allows attackers to write past the leaf page buffer via crafted footer key offsets. Attackers can supply a database file with a corrupted FTS5 index that, when deleted from with secure-delete enabled, corrupts heap memory and crashes the application.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- SQLite SQLite
fixed in 3.54.0
References 7
GitHub · sqlite/sqlite
abraxaslabs.tech
Questions about CVE-2026-119374
What does this mean?
A heap buffer overflow in SQLite's FTS5 secure-delete code can write past the end of a memory buffer. The advisory says this can lead to a buffer overrun when SQLite handles a strategically corrupted database.Source: sqlite.org, sqlite.org
Am I affected, and how do I check?
SQLite versions before 3.54.0 are affected, but only where the FTS5 secure-delete code path is involved, which requires a database with an FTS5 index. To check, look at the SQLite library version in use and whether any database uses FTS5 indexes.Source: sqlite.org, sqlite.org
What should I do about it?
Upgrade to SQLite 3.54.0 or later, which contains the fix. The facts list no workaround.Source: sqlite.org, sqlite.org
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data