How severe is GHSA-h5x4-m2qf-r4f2?

No CVSS score has been assigned to GHSA-h5x4-m2qf-r4f2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h5x4-m2qf-r4f2?

GHSA-h5x4-m2qf-r4f2 affects the following packages: diesel (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-h5x4-m2qf-r4f2?

Update diesel to 2.3.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h5x4-m2qf-r4f2 is resolved across your whole dependency graph.

How do I detect GHSA-h5x4-m2qf-r4f2 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for diesel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-h5x4-m2qf-r4f2 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-h5x4-m2qf-r4f2?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-h5x4-m2qf-r4f2 can be triaged on real exposure rather than presence alone.

Is GHSA-h5x4-m2qf-r4f2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-h5x4-m2qf-r4f2 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-h5x4-m2qf-r4f2 published, and has it been updated?

GHSA-h5x4-m2qf-r4f2 was published on May 5, 2026 and was last updated on June 18, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

GHSA-h5x4-m2qf-r4f2 — diesel

Fix: diesel-rs/diesel#5042

GHSA-h5x4-m2qf-r4f2 is a remote code execution vulnerability in diesel. A fix is available for diesel — see the affected versions and patch details below.

Diesel's SQLite backend has possible UTF-8 corruption

Also known asRUSTSEC-2026-0111

Published

May 5, 2026

Updated

Jun 18, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jun 18, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀diesel

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

Diesel uses the sqlite3_value_text function to receive strings from SQLite while deserializing query results. We misinterpreted the corresponding SQLite 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.

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 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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`diesel`	all versions	2.3.8`cargo update -p diesel --precise 2.3.8`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for diesel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update diesel to 2.3.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h5x4-m2qf-r4f2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-h5x4-m2qf-r4f2 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-h5x4-m2qf-r4f2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-h5x4-m2qf-r4f2 in your dependencies?

O3 Security finds GHSA-h5x4-m2qf-r4f2 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works