{"answers":{"affected":"3 open source packages ship an affected version, including diesel.","exploited":"There is no known exploitation of GHSA-q8x8-jrhj-fh9p in the wild and no public exploit code.","fix":"Upgrade diesel to 2.3.8 or later.","what":"GHSA-q8x8-jrhj-fh9p is a memory corruption vulnerability in diesel, published on 24 Apr 2026."},"fix_prompt":"Check this codebase for GHSA-q8x8-jrhj-fh9p and fix it if it is affected.\n\nWhat it is: GHSA-q8x8-jrhj-fh9p is a memory corruption vulnerability in diesel, published on 24 Apr 2026. \nExploitation: There is no known exploitation of GHSA-q8x8-jrhj-fh9p in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- diesel (crates.io): affected all versions; fixed in 2.3.8\n- diesel (crates.io): affected all versions; fixed in 2.3.8\n- diesel (crates.io): affected from 0.0.0-0; fixed in 2.3.8\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-q8x8-jrhj-fh9p/ (Markdown: https://insights.sbomify.com/GHSA-q8x8-jrhj-fh9p/index.md)","id":"GHSA-q8x8-jrhj-fh9p","markdown":"https://insights.sbomify.com/GHSA-q8x8-jrhj-fh9p/index.md","name":"GHSA-q8x8-jrhj-fh9p","record":{"aliases":["RUSTSEC-2026-0137"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"unknown","non_default_config":true,"product_category":"Rust SQLite ORM","requires_auth":"none","summary":"Unaligned memory access in Diesel's SQLite aggregate implementation can cause crashes or code execution when using custom aligned types.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"Diesel allows to register custom aggregate SQL functions for SQLite via the `SqliteAggregate` interface.\n\nTo 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.\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 allocates the corresponding memory on Rust side to get a correctly aligned allocation.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Diesel: Possible unaligned data access for implementations of `SqliteAggregate`","id":"GHSA-q8x8-jrhj-fh9p","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["2.3.8"],"introduced":["0"],"last_affected":[],"package":"diesel","purl":null,"source":"GHSA-q8x8-jrhj-fh9p"},{"ecosystem":"crates.io","fixed":["2.3.8"],"introduced":["0"],"last_affected":[],"package":"diesel","purl":"pkg:cargo/diesel","source":"GHSA-q8x8-jrhj-fh9p"},{"ecosystem":"crates.io","fixed":["2.3.8"],"introduced":["0.0.0-0"],"last_affected":[],"package":"diesel","purl":"pkg:cargo/diesel","source":"RUSTSEC-2026-0137"}],"products":null,"published":"2026-04-24","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Unaligned memory access in Diesel's SQLite aggregate implementation can cause crashes or code execution when using custom aligned types.","url":"https://insights.sbomify.com/GHSA-q8x8-jrhj-fh9p/"}