CVE-2026-119375VulnerabilityPublished 30 Oct 2026Updated 9 Nov 2026

`libsqlite3-sys` via C SQLite CVE-2026-119375

Affects libsqlite3-sysSource GCVE Database

Compare

Authoritative record:CVE-2026-119375· Medium 6.8

Not known to be exploited · CVSS 6.8 Medium : upgrade to 0.39.0 when convenient.

Data as of 9 Nov 2026, 11:34 UTC

CVSS 4.0 base score

6.8Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (VulnCheck)	CVSS 4.0	6.8
CNA (VulnCheck)	CVSS 3.1	5.5
CNA	CVSS 4.0	6.8

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.39.0

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

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade libsqlite3-sys to 0.39.0.

Affected software

Product	Affected	Fixed in
crates.iolibsqlite3-sys`pkg:cargo/libsqlite3-sys`Other threats	Affected >=0.6.0 <0.39.0	Fixed in 0.39.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in libsqlite3-sys version 0.39.0 and later, which bundles the fixed SQLite version 3.54.0. Users should upgrade to libsqlite3-sys 0.39.0 or newer to remediate this vulnerability. Builds linking against system SQLite are not affected by this crate's bundled SQLite vulnerability but should ensure their system SQLite is updated to a fixed version. No additional mitigation is required beyond applying the official fix.

Description

SQLite versions prior to 3.54.0 have a vulnerability where opening a database file alongside a write-ahead-log file with a differing page size can cause queries to return uninitialized page-cache memory, potentially leaking stale process memory. The Rust crate libsqlite3-sys, when built with its bundled SQLite source between versions 0.6.0 and before 0.39.0, is affected due to bundling vulnerable SQLite versions. The issue requires local access and crafted files. The vulnerability is fixed in libsqlite3-sys version 0.39.0, which bundles SQLite 3.54.0.

Impact

An attacker with local access who can cause a process to open a crafted database file and its associated write-ahead-log file with differing page sizes may cause the process to return uninitialized memory from its page cache. This could lead to disclosure of stale memory contents from the process, potentially exposing sensitive information. The vulnerability requires local access and crafted files; remote exploitation is not indicated. The impact is limited to information disclosure of process memory.

References

Community reviews

Loading reviews…