# diesel-async may expose uninitialized padding bytes for MySQL temporal columns

Advisory record · `GHSA-ff9q-rm55-q7qr`

- **Identifiers:** `GHSA-ff9q-rm55-q7qr`
- **State:** Confirmed
- **Severity:** CVSS 4.0, no score published
- **Critical:** No
- **Weakness (CWE):** [CWE-126](https://cwe.mitre.org/data/definitions/126.html)
- **Tags:** [CWE-126](https://agentprime.io/advisories/tag/cwe-126.md)
- **Published:** 7 May 2026
- **Updated:** 7 May 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 7 May 2026, 00:02 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `diesel-async` (crates.io): affected `>=0.1.0, <0.9.0`; fixed in `0.9.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> diesel-async versions 0.1.0 up to but not including 0.9.0 expose uninitialized padding bytes to safe code when reading MySQL DATE, TIME, DATETIME, or TIMESTAMP columns. An attacker who can get a query returning such a column to run through the affected library could read those bytes, which may hold stale heap or stack contents, and reading them is undefined behavior. Upgrade to diesel-async 0.9.0 or later.

Written 8 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- Score not published, CVSS 4.0: `CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 15:18 UTC: First seen by agentprime
- 31 Oct 2026, 15:18 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-ff9q-rm55-q7qr)

## Sources

- [GitHub Advisory Database: GHSA-ff9q-rm55-q7qr](https://github.com/advisories/GHSA-ff9q-rm55-q7qr)
- [OSV: GHSA-ff9q-rm55-q7qr](https://osv.dev/vulnerability/GHSA-ff9q-rm55-q7qr)
- <https://github.com/diesel-rs/diesel_async/security/advisories/GHSA-ff9q-rm55-q7qr>
- <https://github.com/diesel-rs/diesel_async/commit/18f2c861c51b4a5f23a20bd749eba13737b9e4aa>
- <https://github.com/diesel-rs/diesel_async>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-ff9q-rm55-q7qr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-ff9q-rm55-q7qr/>. Everything for agents: <https://agentprime.io/llms.txt>.