How severe is GHSA-xrv3-jmcp-374j?

GHSA-xrv3-jmcp-374j has a CVSS score of 6.2/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-xrv3-jmcp-374j?

GHSA-xrv3-jmcp-374j affects the following packages: zerovec (crates.io), zerovec (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-xrv3-jmcp-374j?

Update zerovec to 0.10.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xrv3-jmcp-374j is resolved across your whole dependency graph.

How do I detect GHSA-xrv3-jmcp-374j in my crates.io dependencies?

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

How do I mitigate GHSA-xrv3-jmcp-374j 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-xrv3-jmcp-374j actively exploited in the wild?

No public exploit code has been indexed for GHSA-xrv3-jmcp-374j 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-xrv3-jmcp-374j published, and has it been updated?

GHSA-xrv3-jmcp-374j was published on July 8, 2024 and was last updated on September 10, 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

MEDIUM severity

zerovec incorrectly uses `#[repr(packed)]`GHSA-xrv3-jmcp-374j

MEDIUM

GHSA-xrv3-jmcp-374j is a medium-severity (CVSS 6.2) vulnerability in zerovec. A fix is available for zerovec — see the affected versions and patch details below.

Also known asRUSTSEC-2024-0347

Published

Jul 8, 2024

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🦀zerovec🦀zerovec

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

The affected versions make unsafe memory accesses under the assumption that #[repr(packed)] has a guaranteed field order.

The Rust specification does not guarantee this, and https://github.com/rust-lang/rust/pull/125360 (1.80.0-beta) starts reordering fields of #[repr(packed)] structs, leading to illegal memory accesses.

The patched versions 0.9.7 and 0.10.4 use #[repr(C, packed)], which guarantees field order.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`zerovec`	≥ 0.10.0&&< 0.10.4	0.10.4`cargo update -p zerovec --precise 0.10.4`
🦀crates.io	`zerovec`	all versions	0.9.7`cargo update -p zerovec --precise 0.9.7`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zerovec, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update zerovec to 0.10.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xrv3-jmcp-374j 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

The affected versions make unsafe memory accesses under the assumption that `#[repr(packed)]` has a guaranteed field order. The Rust specification does not guarantee this, and https://github.com/rust-lang/rust/pull/125360 (1.80.0-beta) starts reordering fields of `#[repr(packed)]` structs, leading to illegal memory accesses. The patched versions `0.9.7` and `0.10.4` use `#[repr(C, packed)]`, which guarantees field order.

O3 Security · Impact-Aware SCA

Is GHSA-xrv3-jmcp-374j in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works