PT-2026-49258 · Crates.Io · Diesel
Published
2026-06-05
·
Updated
2026-06-05
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
Diesel allows loading a SQLite database from a byte buffer, represented as
&[u8], at runtime via the SqliteConnection::deserialize readonly database function. In previous versions of Diesel, this buffer was passed directly to libsqlite3. Since libsqlite3 requires the buffer to remain alive for as long as the database connection is open and Diesel did not ensure this as part of its safe API, callers of SqliteConnection::deserialize readonly database could drop the buffer prematurely. This prematurely drop caused libsqlite3 to operate on freed memory.This vulnerability affects users of
SqliteConnection::deserialize readonly database who drop the buffer passed to the function before they drop the database connection.Mitigation
The preferred mitigation to the outlined problem is to update to Diesel version 2.3.10 or newer, which includes a fix for the problem. Alternatively users need to take to keep the buffer alive until the connection is dropped.
Resolution
Diesel now stores a copy of the buffer inside of the
SqliteConnection object itself to keep it alive as long as the underlying libsqlite3 connection exists. Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Diesel