How severe is GHSA-74r5-g7vc-j2v2?

GHSA-74r5-g7vc-j2v2 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-74r5-g7vc-j2v2?

GHSA-74r5-g7vc-j2v2 affects the following packages: zerovec-derive (crates.io), zerovec-derive (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-74r5-g7vc-j2v2?

Update zerovec-derive to 0.10.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-74r5-g7vc-j2v2 is resolved across your whole dependency graph.

How do I detect GHSA-74r5-g7vc-j2v2 in my crates.io dependencies?

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

How do I mitigate GHSA-74r5-g7vc-j2v2 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.

How does O3 Security protect against GHSA-74r5-g7vc-j2v2?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-74r5-g7vc-j2v2 can be triaged on real exposure rather than presence alone.

Is GHSA-74r5-g7vc-j2v2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-74r5-g7vc-j2v2 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-74r5-g7vc-j2v2 published, and has it been updated?

GHSA-74r5-g7vc-j2v2 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

GHSA-74r5-g7vc-j2v2 — zerovec-derive

MEDIUMFix: rustsec/advisory-db#2007

GHSA-74r5-g7vc-j2v2 is a medium-severity (CVSS 6.2) vulnerability in zerovec-derive. A fix is available for zerovec-derive — see the affected versions and patch details below.

zerovec-derive incorrectly uses `#[repr(packed)]`

Also known asRUSTSEC-2024-0346

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-derive🦀zerovec-derive

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.3 use #[repr(C, packed)], which guarantees field order.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`zerovec-derive`	≥ 0.10.0&&< 0.10.3	0.10.3`cargo update -p zerovec-derive --precise 0.10.3`
🦀crates.io	`zerovec-derive`	all versions	0.9.7`cargo update -p zerovec-derive --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-derive, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update zerovec-derive to 0.10.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-74r5-g7vc-j2v2 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-74r5-g7vc-j2v2 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-74r5-g7vc-j2v2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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.3` use `#[repr(C, packed)]`, which guarantees field order.

O3 Security · Impact-Aware SCA

Is GHSA-74r5-g7vc-j2v2 in your dependencies?

O3 Security finds GHSA-74r5-g7vc-j2v2 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works