Diesel has possible use after free when deserializing a SQLite database via SqliteConnection::deserialize_readonly_database

Exploitation

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

CVSS 4.0

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

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Diesel allows loading a SQLite database from a byte buffer, represented as &[u8], at runtime via the SqliteConnection::deserializereadonlydatabase function. In previous versions of Diesel, this buffer was passed directly to libsqlite3. Since libsqlite3 requires the buffer to remain alive for as long as the database connection is open and Diesel did not ensure this as part of its safe API, callers of SqliteConnection::deserializereadonlydatabase could drop the buffer prematurely. This prematurely drop caused libsqlite3 to operate on freed memory. This vulnerability affects users of SqliteConnection::deserializereadonlydatabase who drop the buffer passed to the function before they drop the database connection. Mitigation The preferred mitigation to the outlined problem is to update to Diesel version 2.3.10 or newer, which includes a fix for the problem. Alternatively users need to take to keep the buffer alive until the connection is dropped. Resolution Diesel now stores a copy of the…

Published by the source

16 Jul 2026, 19:25 UTC

Last modified by the source

16 Jul 2026, 19:25 UTC

Source last checked

26 Oct 2026, 15:43 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-ggxf-9f6j-w742

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

# Patch Next advisory brief: GHSA-ggxf-9f6j-w742

Advisory: Diesel has possible use after free when deserializing a SQLite database via `SqliteConnection::deserialize_readonly_database`
IDs: GHSA-ggxf-9f6j-w742
Record: https://patchnext.com/advisories/ghsa-ggxf-9f6j-w742 (revision 1, source checked 26 Oct 2026, 15:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
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.10. A vendor fix does not mean a deployment is fixed.

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

## 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-ggxf-9f6j-w742 (GitHub-reviewed advisory GHSA-ggxf-9f6j-w742 lists affected ranges: crates.io diesel >=0 <2.3.10)

Commands are suggestions: review each one before running it.