RUSTSEC-2026-0502 (CVE-2026-119375)
Vulnerability from osv_rustsec – Published: 2026-10-30 12:00 – Updated: 2026-11-12 07:53 – Source websiteSQLite 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.
sqlcipher-src ships the SQLCipher amalgamation (SQLCipher is built on SQLite and contains the same sqlite3WalReadFrame code) for -sys crates to compile, so a build that uses it is susceptible to the vulnerability. The releases 419.0.3 to 419.0.6 bundle SQLCipher 4.19.0 on SQLite 3.53.4 and are affected. sqlcipher-src was updated in 420.0.0 (SQLCipher 4.20.0 on SQLite 3.54.1), which contains the fix. The releases 0.1.0 and 0.1.1 contain no SQLCipher source. libsqlite3-sys 0.39.0 and 0.39.1 depend on sqlcipher-src =419.0.6 for their bundled-sqlcipher feature.
Only a process that opens a database file, with its -wal, that a less trusted party could have written is exposed.
{
"affected": [
{
"database_specific": {
"categories": [
"memory-exposure"
],
"cvss": "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",
"informational": null
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "sqlcipher-src",
"purl": "pkg:cargo/sqlcipher-src"
},
"ranges": [
{
"events": [
{
"introduced": "419.0.3"
},
{
"fixed": "420.0.0"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"CVE-2026-119375",
"GHSA-72w2-rjgg-q729"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "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\u0027s. A crafted pair of files can make ordinary queries return stale bytes from the process\u0027s memory. The attack vector is local and needs the victim to open the files.\n\n`sqlcipher-src` ships the SQLCipher amalgamation (SQLCipher is built on SQLite and contains the same `sqlite3WalReadFrame` code) for `-sys` crates to compile, so a build that uses it is susceptible to the vulnerability. The releases `419.0.3` to `419.0.6` bundle SQLCipher `4.19.0` on SQLite `3.53.4` and are affected. `sqlcipher-src` was updated in `420.0.0` (SQLCipher `4.20.0` on SQLite `3.54.1`), which contains the fix. The releases `0.1.0` and `0.1.1` contain no SQLCipher source. `libsqlite3-sys` `0.39.0` and `0.39.1` depend on `sqlcipher-src =419.0.6` for their `bundled-sqlcipher` feature.\n\nOnly a process that opens a database file, with its `-wal`, that a less trusted party could have written is exposed.",
"id": "RUSTSEC-2026-0502",
"modified": "2026-11-12T07:53:20Z",
"published": "2026-10-30T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/sqlcipher-src"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2026-0502.html"
},
{
"type": "WEB",
"url": "https://sqlite.org/bugs/info/2026-08-17T15:54:41Z"
},
{
"type": "WEB",
"url": "https://github.com/sqlite/sqlite/commit/e5bf119821f25be1d7f10ef0a2edbe175289166e"
},
{
"type": "WEB",
"url": "https://sqlite.org/releaselog/3_54_0.html"
}
],
"related": [],
"severity": [
{
"score": "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",
"type": "CVSS_V4"
}
],
"summary": "`sqlcipher-src` via C SQLite CVE-2026-119375"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.