Advisory

GHSA-h5x4-m2qf-r4f2

Also known as: RUSTSEC-2026-0111

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 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.

Mitigation

The preferred mitigation to the outlined problem is to update to a Diesel version 2.3.8 or newer, which includes fixes for the problem.

Resolution

Diesel 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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-05-05 18:08 UTC
Modified
2026-06-18 20:30 UTC

Affected packages and fixes

diesel

crates.io · All systems

Affected

  • introduced 0, fixed 2.3.8 (semver)

Fixed versions

2.3.8

Fix

  • Fixed version 2.3.8
    cargo update -p diesel --precise 2.3.8

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences