Diesel's SQLite backend has possible UTF-8 corruption

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Diesel uses the sqlite3valuetext 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 cchar. Based on that we used str::fromutf8unchecked 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::fromutf8unchecked 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…

Published by the source

5 May 2026, 18:08 UTC

Last modified by the source

18 Jun 2026, 20:21 UTC

Source last checked

26 Oct 2026, 15:42 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-h5x4-m2qf-r4f2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-h5x4-m2qf-r4f2

Advisory: Diesel's SQLite backend has possible UTF-8 corruption
IDs: GHSA-h5x4-m2qf-r4f2
Record: https://patchnext.com/advisories/ghsa-h5x4-m2qf-r4f2 (revision 1, source checked 26 Oct 2026, 15:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: diesel 2.3.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io diesel: affected < 2.3.8; fixed in 2.3.8

## Suggested inspection (read-only)
- crates.io diesel: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on diesel.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-h5x4-m2qf-r4f2 (GitHub-reviewed advisory GHSA-h5x4-m2qf-r4f2 lists affected ranges: crates.io diesel >=0 <2.3.8)

Commands are suggestions: review each one before running it.