SQLite before 3.54.0 Heap Buffer Overflow via Session Extension sessionUpdateFind()
Only affects SQLite before 3.54.0 built with SQLITE_ENABLE_SESSION that applies changesets from untrusted sources. 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, a widely used embedded database engine, is affected when it is built with the session extension and version 3.54.0 or later is not in use. An attacker who supplies a specially crafted changeset could corrupt heap memory, which could crash the application or potentially allow further malicious behavior.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
SQLite before 3.54.0 built with the session extension contains a heap buffer overflow vulnerability in sqlite3changeset_apply() that allows attackers to corrupt heap memory by supplying crafted changesets. Attackers can repeat a table name in a second changeset block with a larger column count, causing sessionUpdateFind() to memset past the undersized aUpdateMask allocation.
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 8
GitHub · sqlite/sqlite
abraxaslabs.tech
Questions about CVE-2026-119379
What does this mean?
The bug is a heap out-of-bounds write, which corrupts heap memory inside the library process. It is triggered by a crafted changeset passed to sqlite3changeset_apply() or related apply APIs.Source: sqlite.org
Am I affected, and how do I check?
Versions before 3.54.0 are affected, but only when the library is built with SQLITE_ENABLE_SESSION and the application passes changesets from an untrusted source to sqlite3changeset_apply() or related apply APIs. To check, look at the version reported by sqlite3 --version or sqlite3_libversion(), and at whether the build defines SQLITE_ENABLE_SESSION.Source: sqlite.org
What should I do about it?
Upgrade to SQLite 3.54.0 or later, which contains the fix.Source: 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