How severe is GHSA-q8x8-jrhj-fh9p?

No CVSS score has been assigned to GHSA-q8x8-jrhj-fh9p yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q8x8-jrhj-fh9p?

GHSA-q8x8-jrhj-fh9p affects the following packages: diesel (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-q8x8-jrhj-fh9p?

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

How do I detect GHSA-q8x8-jrhj-fh9p 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-q8x8-jrhj-fh9p if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-q8x8-jrhj-fh9p actively exploited in the wild?

No public exploit code has been indexed for GHSA-q8x8-jrhj-fh9p 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-q8x8-jrhj-fh9p published, and has it been updated?

GHSA-q8x8-jrhj-fh9p was published on May 19, 2026 and was last updated on May 20, 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-q8x8-jrhj-fh9p — diesel

Fix: diesel-rs/diesel#5042

GHSA-q8x8-jrhj-fh9p is a security vulnerability in diesel. A fix is available for diesel — see the affected versions and patch details below.

Diesel: Possible unaligned data access for implementations of `SqliteAggregate`

Also known asRUSTSEC-2026-0137

Published

May 19, 2026

Updated

May 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of May 20, 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 to register custom aggregate SQL functions for SQLite via the SqliteAggregate interface.

To store an instance of the custom aggregate processor Diesel relied on the sqlite3_aggregate_context function provided by sqlite. This function doesn't provide any guarantees about alignment of the returned allocation, which in turn can lead to problems if the type implementing requires a special alignment, e.g. via a custom #[align(x)] attribute on the type implementing this trait. This affects any user of SqliteAggregate that registers the custom aggregate function with an SQLite connection, while using a non-standard alignment on the type implementing this trait.

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 allocates the corresponding memory on Rust side to get a correctly aligned allocation.

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-q8x8-jrhj-fh9p is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

Diesel allows to register custom aggregate SQL functions for SQLite via the `SqliteAggregate` interface. To store an instance of the custom aggregate processor Diesel relied on the `sqlite3_aggregate_context` function provided by sqlite. This function doesn't provide any guarantees about alignment of the returned allocation, which in turn can lead to problems if the type implementing requires a special alignment, e.g. via a custom `#[align(x)]` attribute on the type implementing this trait. This affects any user of `SqliteAggregate` that registers the custom aggregate function with an SQLite

O3 Security · Impact-Aware SCA

Is GHSA-q8x8-jrhj-fh9p in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works