libsqlite3-sys via C SQLite CVE-2026-119375

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.8 · CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-119375: 0.19% estimated exploitation activity in the next 30 days; percentile 9.24 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

SQLite versions before 3.54.0 can return uninitialized page-cache memory when a process opens a database file together with a sibling write-ahead-log (`-wal`) file whose page size differs from the database's. A crafted pair of files can make ordinary queries return stale bytes from the process's memory. The attack vector is local and needs the victim to open the files. As `libsqlite3-sys` bundles SQLite when it is built from its bundled source (the `bundled` feature, which `rusqlite`'s `bundled` feature enables), it is susceptible to the vulnerability. The releases `0.6.0` to `0.38.2` bundle SQLite `3.13.0` to `3.53.2` and are affected; the earlier releases contain no SQLite source. `libsqlite3-sys` was updated to bundle the patched version of SQLite in `0.39.0` (SQLite `3.54.0`) and `0.39.1` (SQLite `3.54.1`), released with `rusqlite` 0.41. `libsqlite3-sys` `0.39` declares Rust 1.88 and `rusqlite` `0.41` declares Rust…

Published by the source

30 Oct 2026, 12:00 UTC

Last modified by the source

9 Nov 2026, 10:00 UTC

Source last checked

10 Nov 2026, 06:45 UTC

1. Revision 1 · created · 10 Nov 2026

   Published from osv record RUSTSEC-2026-0459

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-119375

Advisory: `libsqlite3-sys` via C SQLite CVE-2026-119375
IDs: CVE-2026-119375, GHSA-72w2-rjgg-q729
Record: https://patchnext.com/advisories/cve-2026-119375 (revision 1, source checked 10 Nov 2026, 06:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: libsqlite3-sys 0.39.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io libsqlite3-sys: affected >= 0.6.0, < 0.39.0; fixed in 0.39.0

## Suggested inspection (read-only)
- crates.io libsqlite3-sys: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on libsqlite3-sys.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/RUSTSEC-2026-0459 (OSV record RUSTSEC-2026-0459 lists affected ranges: crates.io libsqlite3-sys >=0.6.0 <0.39.0 (fixed))

Commands are suggestions: review each one before running it.