{"answers":{"affected":"3 open source packages ship an affected version, including diesel.","exploited":"There is no known exploitation of GHSA-h5x4-m2qf-r4f2 in the wild and no public exploit code.","fix":"Upgrade diesel to 2.3.8 or later.","what":"GHSA-h5x4-m2qf-r4f2 is a memory corruption vulnerability in diesel, published on 24 Apr 2026."},"fix_prompt":"Check this codebase for GHSA-h5x4-m2qf-r4f2 and fix it if it is affected.\n\nWhat it is: GHSA-h5x4-m2qf-r4f2 is a memory corruption vulnerability in diesel, published on 24 Apr 2026. \nExploitation: There is no known exploitation of GHSA-h5x4-m2qf-r4f2 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-h5x4-m2qf-r4f2/ (Markdown: https://insights.sbomify.com/GHSA-h5x4-m2qf-r4f2/index.md)","id":"GHSA-h5x4-m2qf-r4f2","markdown":"https://insights.sbomify.com/GHSA-h5x4-m2qf-r4f2/index.md","name":"GHSA-h5x4-m2qf-r4f2","record":{"aliases":["RUSTSEC-2026-0111"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust SQLite library","requires_auth":"none","summary":"An attacker can cause memory corruption or crashes in applications using Diesel with SQLite by providing invalid UTF-8 data in BLOB fields.","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 uses the `sqlite3_value_text` function to receive strings from SQLite while deserializing query results. We misinterpreted the corresponding [SQLite](https://sqlite.org/c3ref/value_blob.html) 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.\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 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.","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":"Possible UTF-8 corruption in Diesels SQLite backend","id":"GHSA-h5x4-m2qf-r4f2","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-h5x4-m2qf-r4f2"},{"ecosystem":"crates.io","fixed":["2.3.8"],"introduced":["0"],"last_affected":[],"package":"diesel","purl":"pkg:cargo/diesel","source":"GHSA-h5x4-m2qf-r4f2"},{"ecosystem":"crates.io","fixed":["2.3.8"],"introduced":["0.0.0-0"],"last_affected":[],"package":"diesel","purl":"pkg:cargo/diesel","source":"RUSTSEC-2026-0111"}],"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":"An attacker can cause memory corruption or crashes in applications using Diesel with SQLite by providing invalid UTF-8 data in BLOB fields.","url":"https://insights.sbomify.com/GHSA-h5x4-m2qf-r4f2/"}