{"id":"GHSA-h5x4-m2qf-r4f2","aliases":["RUSTSEC-2026-0111"],"url":"https://o3.security/vulnerability/GHSA-h5x4-m2qf-r4f2","summary":"Diesel's SQLite backend has possible UTF-8 corruption","details":"Diesel uses the `sqlite3_value_text` function to receive strings from SQLite while deserializing query results. We misinterpreted the corresponding [SQLite](https://sqlite.org/c3ref/value_blob.html) documentation that this function always returns a UTF-8 encoded string values as `*const c_char`. Based on that we used `str::from_utf8_unchecked` to construct a Rust string slice without any additional UTF-8 checks in place. It turned out that this function doesn't always return correct UTF-8 strings. For field of the SQLite side storage type `BLOB` this pointer can contain arbitrary bytes, which makes the usage of `str::from_utf8_unchecked` unsound as this violates the safety contract of `str` to only contain valid UTF-8 encoded Strings.\n\n## Mitigation\n\nThe preferred mitigation to the outlined problem is to update to a Diesel version 2.3.8 or newer, which includes fixes for the problem.\n\n## Resolution\n\nDiesel now correctly checks whether the provides byte buffer is actually valid UTF-8, instead of relying on SQLite's documentation. This fix is included in the `2.3.8` release.","published":"2026-05-05T18:08:05Z","modified":"2026-06-18T20:30:23.851810890Z","cvss":null,"epss":null,"cisaKev":null,"exploitsKnown":0,"affectedPackages":[{"ecosystem":"crates.io","name":"diesel","fixedVersion":"2.3.8"}],"fix":{"url":"https://github.com/diesel-rs/diesel/pull/5042","label":"diesel-rs/diesel#5042"},"references":[{"type":"WEB","url":"https://github.com/diesel-rs/diesel/pull/5042"},{"type":"PACKAGE","url":"https://github.com/diesel-rs/diesel"},{"type":"WEB","url":"https://rustsec.org/advisories/RUSTSEC-2026-0111.html"}],"provenance":{"sources":["OSV.dev","FIRST.org (EPSS)"],"lastVerified":"2026-06-18T20:30:23.851810890Z"}}