Quick answers
- Is CVE-2026-119375 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119375 being exploited in the wild.
- How severe is CVE-2026-119375?
- Medium severity, with a CVSS score of 5.5, published 30 October 2026.
- Which products and versions are affected?
- libsqlite3-sys (crates.io) SEMVER:introduced=0.6.0,fixed=0.39.0; Sqlite before 3.54.0.
- Is there a fix for CVE-2026-119375?
- Yes. libsqlite3-sys (crates.io): upgrade to 0.39.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119375 attacked?
- It is attacked over the network or with local access.
- Am I affected by CVE-2026-119375?
- Check whether you run libsqlite3-sys (crates.io) or 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
- libsqlite3-sys (crates.io): upgrade to 0.39.0 or later
cargo update -p libsqlite3-sys
Technical details
The vulnerability exists in SQLite's Write-Ahead Logging (WAL) page-cache handling when processing a WAL file with an undersized page size. An attacker can supply a crafted database and WAL file whose oversized record payloads cause functions like substr() to return stale bytes from uninitialized memory. This allows disclosure of other table rows and internal pointers without requiring authentication or special privileges.
Affected products
- SQLite SQLite before 3.54.0
Identifiers
- CVE-2026-119375
- GHSA-72w2-rjgg-q729
- RUSTSEC-2026-0459
Timeline
- 2026-10-30: advisory