Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Medium severity, with a CVSS score of 6.9, published 16 July 2026.
- Which products and versions are affected?
- diesel (crates.io) < 2.3.10.
- Is there a fix for This vulnerability?
- A patch was published on 2026-07-16: Version 2.3.10 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run diesel (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A use-after-free vulnerability exists in Diesel's SQLite backend due to improper lifetime management of memory buffers. When using `SqliteConnection::deserialize_readonly_database`, Diesel passed a byte slice (`&[u8]`) directly to `libsqlite3` without ensuring the buffer's lifetime matched the connection's lifetime. If a caller drops the buffer while the connection remains open, `libsqlite3` may attempt to access freed memory. This is reachable if an attacker can influence the data or timing of database deserialization in an application. The issue is resolved in version 2.3.10 by having `SqliteConnection` take ownership of a copy of the buffer.
Affected products
- diesel-rs diesel < 2.3.10
Timeline
- 2026-06-05: disclosed: Reported via RustSec
- 2026-07-16: advisory: GitHub Advisory published
- 2026-07-16: patched: Version 2.3.10 released