Vulnerability MediumRUSTSEC-2026-0137 · diesel
RUSTSEC-2026-0137: Possible unaligned data access for implementations of `SqliteAggregate`
Short answerA security vulnerability in the diesel crate: Possible unaligned data access for implementations of `SqliteAggregate`. GitHub rates it Medium. Fixed in 2.3.8: update to a fixed version.
| Crate | diesel |
|---|---|
| Type | Vulnerability |
| Affected versions | Before 2.3.8. |
| Fixed in | 2.3.8 |
| Severity | Medium (GitHub rating) |
| Published | 2026-04-24 |
| Last changed | 2026-05-20 |
| Also known as | GHSA-q8x8-jrhj-fh9p |
| Affected functions | diesel::sqlite::SqliteAggregate |
What to do
- See which version you have:
cargo tree -i diesel(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p diesel. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplediesel = "2.3.8") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
Diesel allows to register custom aggregate SQL functions for SQLite via the SqliteAggregate interface.
To store an instance of the custom aggregate processor Diesel relied on the sqlite3_aggregate_context function provided by sqlite. This function doesn't provide any guarantees about alignment of the returned allocation, which in turn can lead to problems if the type implementing requires a special alignment, e.g. via a custom #[align(x)] attribute on the type implementing this trait. This affects any user of SqliteAggregate that registers the custom aggregate function with an SQLite connection, while using a non-standard alignment on the type implementing this trait.
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 allocates the corresponding memory on Rust side to get a correctly aligned allocation.
References
- Package: crates.io/crates/diesel
- Advisory: rustsec.org/advisories/RUSTSEC-2026-0137.html
- Web: github.com/diesel-rs/diesel/pull/5042
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for diesel
- Vulnerability CriticalRUSTSEC-2021-0037 · 2021-03-05Fix a use-after-free bug in diesels Sqlite backend
- VulnerabilityRUSTSEC-2024-0365 · 2024-08-23Binary Protocol Misinterpretation caused by Truncating or Overflowing Casts
- UnsoundRUSTSEC-2026-0111 · 2026-04-24Possible UTF-8 corruption in Diesels SQLite backend
- UnsoundRUSTSEC-2026-0134 · 2026-04-24Unsound access to padding bytes while serializing date/time values using the Mysql backend
- UnsoundRUSTSEC-2026-0135 · 2026-04-24Unsound transmute while debug/display printing batch Insert statements in Diesel's SQLite backend
- VulnerabilityRUSTSEC-2026-0136 · 2026-04-24Command injection in Diesel's implementation of `COPY FROM`/`COPY TO`
- UnsoundRUSTSEC-2026-0172 · 2026-06-05Possible use after free when deserializing a SQLite database via `SqliteConnection::deserialize_readonly_database`
Up next
Same cratediesel: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?