How severe is GHSA-qm2p-4w45-v2vr?

No CVSS score has been assigned to GHSA-qm2p-4w45-v2vr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qm2p-4w45-v2vr?

GHSA-qm2p-4w45-v2vr affects the following packages: grcov (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-qm2p-4w45-v2vr?

Update grcov to 0.8.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qm2p-4w45-v2vr is resolved across your whole dependency graph.

How do I detect GHSA-qm2p-4w45-v2vr in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for grcov, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-qm2p-4w45-v2vr if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is GHSA-qm2p-4w45-v2vr actively exploited in the wild?

No public exploit code has been indexed for GHSA-qm2p-4w45-v2vr 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-qm2p-4w45-v2vr published, and has it been updated?

GHSA-qm2p-4w45-v2vr was published on February 10, 2025 and was last updated on October 28, 2025. 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

grcov has an out of bounds write triggered by crafted coverage dataGHSA-qm2p-4w45-v2vr

Fix: mozilla/grcov@c821956

GHSA-qm2p-4w45-v2vr is a remote code execution vulnerability in grcov. A fix is available for grcov — see the affected versions and patch details below.

Also known asRUSTSEC-2025-0005

Published

Feb 10, 2025

Updated

Oct 28, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 28, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀grcov

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

Function grcov::covdir::get_coverage uses the unsafe function get_unchecked_mut without validating that the index is in bounds.

This results in memory corruption, and could potentially allow arbitrary code execution provided that an attacker can feed the tool crafted coverage data.

Affected Packages

1 total 1 fixed

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

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for grcov, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update grcov to 0.8.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qm2p-4w45-v2vr is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

Function `grcov::covdir::get_coverage` uses the `unsafe` function `get_unchecked_mut` without validating that the index is in bounds. This results in memory corruption, and could potentially allow arbitrary code execution provided that an attacker can feed the tool crafted coverage data.

O3 Security · Impact-Aware SCA

Is GHSA-qm2p-4w45-v2vr in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works