How severe is GHSA-ggxf-9f6j-w742?

No CVSS score has been assigned to GHSA-ggxf-9f6j-w742 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-ggxf-9f6j-w742?

GHSA-ggxf-9f6j-w742 affects the following packages: diesel (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-ggxf-9f6j-w742?

Update diesel to 2.3.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ggxf-9f6j-w742 is resolved across your whole dependency graph.

How do I detect GHSA-ggxf-9f6j-w742 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-ggxf-9f6j-w742 if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is GHSA-ggxf-9f6j-w742 actively exploited in the wild?

No public exploit code has been indexed for GHSA-ggxf-9f6j-w742 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-ggxf-9f6j-w742 published, and has it been updated?

GHSA-ggxf-9f6j-w742 was published on July 16, 2026 and was last updated on July 17, 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

Diesel has possible use after free when deserializing a SQLite database via `SqliteConnection::deserialize_readonly_database`GHSA-ggxf-9f6j-w742

Fix: diesel-rs/diesel@1bc2ea4

GHSA-ggxf-9f6j-w742 is a remote code execution vulnerability in diesel. A fix is available for diesel — see the affected versions and patch details below.

Also known asRUSTSEC-2026-0172

Published

Jul 16, 2026

Updated

Jul 17, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jul 17, 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 allows loading a SQLite database from a byte buffer, represented as &[u8], at runtime via the SqliteConnection::deserialize_readonly_database 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::deserialize_readonly_database could drop the buffer prematurely. This prematurely drop caused libsqlite3 to operate on freed memory.

This vulnerability affects users of SqliteConnection::deserialize_readonly_database 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 buffer inside of the SqliteConnection object itself to keep it alive as long as the underlying libsqlite3 connection exists.

Affected Packages

1 total 1 fixed

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

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.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ggxf-9f6j-w742 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

Diesel allows loading a SQLite database from a byte buffer, represented as `&[u8]`, at runtime via the `SqliteConnection::deserialize_readonly_database` 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::deserialize_readonly_database` could drop the buffer prematurely. This prematurely drop caused libsqlite3 to operate on freed memory. This vulnerability affects users of `

O3 Security · Impact-Aware SCA

Is GHSA-ggxf-9f6j-w742 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works