How severe is GHSA-m9p2-fxp5-v3fp?

No CVSS score has been assigned to GHSA-m9p2-fxp5-v3fp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m9p2-fxp5-v3fp?

GHSA-m9p2-fxp5-v3fp affects the following packages: diesel (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-m9p2-fxp5-v3fp?

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

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-m9p2-fxp5-v3fp actively exploited in the wild?

No public exploit code has been indexed for GHSA-m9p2-fxp5-v3fp 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-m9p2-fxp5-v3fp published, and has it been updated?

GHSA-m9p2-fxp5-v3fp 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-m9p2-fxp5-v3fp — diesel

Fix: diesel-rs/diesel#5042

GHSA-m9p2-fxp5-v3fp is a security vulnerability in diesel. A fix is available for diesel — see the affected versions and patch details below.

Diesel: Command injection in Diesel's implementation of `COPY FROM`/`COPY TO`

Also known asRUSTSEC-2026-0136

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 users to configure various options for PostgreSQL's COPY FROM and COPY TO statements. These configurations are partially provided as strings or characters.

Diesel did not check if any these user-provided options contain a quote character ', which can lead to the injection of additional options in the current COPY FROM/COPY TO statement.

This vulnerability affects any user of COPY FROM/COPY TO that passes user-provided input to any of the affected functions. It can result in modifications of options in the current statement, but it is not possible inject additional statements.

Mitigation

The preferred mitigation to the outlined problem is to update to Diesel version 2.3.8 or newer, which includes fixes for the problem.

Resolution

Diesel now correctly escapes any quotes contained in the provided arguments.

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-m9p2-fxp5-v3fp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Diesel allows users to configure various options for PostgreSQL's `COPY FROM` and `COPY TO` statements. These configurations are partially provided as strings or characters. Diesel did not check if any these user-provided options contain a quote character `'`, which can lead to the injection of additional options in the current `COPY FROM`/`COPY TO` statement. This vulnerability affects any user of `COPY FROM`/`COPY TO` that passes user-provided input to any of the affected functions. It can result in modifications of options in the current statement, but it is not possible inject addition

O3 Security · Impact-Aware SCA

Is GHSA-m9p2-fxp5-v3fp in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works