Quick answers
- Is CVE-2026-119379 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119379 being exploited in the wild.
- How severe is CVE-2026-119379?
- High severity, with a CVSS score of 7.8, published 30 October 2026.
- Which products and versions are affected?
- Sqlite before 3.54.0.
- Is there a fix for CVE-2026-119379?
- 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-119379 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-119379?
- 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 heap buffer overflow exists in the sqlite3changeset_apply() function within SQLite's session extension. The vulnerability occurs when an attacker supplies a changeset that repeats a table name with a larger column count in a second block, causing sessionUpdateFind() to write past the bounds of an undersized aUpdateMask allocation. The attack requires the application to process attacker-controlled changesets, but does not require authentication or user interaction beyond changeset input.
Affected products
- SQLite SQLite before 3.54.0
Timeline
- 2026-10-30: disclosed