What is GHSA-XRV3-JMCP-374J?

GHSA-XRV3-JMCP-374J is a medium-severity security vulnerability in zerovec (rust), affecting versions >= 0.10.0, < 0.10.4. It is fixed in 0.10.4, 0.9.7.

How severe is GHSA-XRV3-JMCP-374J?

GHSA-XRV3-JMCP-374J has a CVSS score of 6.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of zerovec are affected by GHSA-XRV3-JMCP-374J?

zerovec (rust) versions >= 0.10.0, < 0.10.4 is affected.

Is there a fix for GHSA-XRV3-JMCP-374J?

Yes. GHSA-XRV3-JMCP-374J is fixed in 0.10.4, 0.9.7. Upgrade to this version or later.

Is GHSA-XRV3-JMCP-374J exploitable, and should I be worried?

Whether GHSA-XRV3-JMCP-374J is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-XRV3-JMCP-374J is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-XRV3-JMCP-374J?

Upgrade: zerovec to 0.10.4 or later, zerovec to 0.9.7 or later.

GHSA-XRV3-JMCP-374J in zerovec

Q: How severe is GHSA-XRV3-JMCP-374J?

GHSA-XRV3-JMCP-374J has a CVSS score of 6.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of zerovec are affected by GHSA-XRV3-JMCP-374J?

zerovec (rust) versions >= 0.10.0, < 0.10.4 is affected.

Q: Is there a fix for GHSA-XRV3-JMCP-374J?

Yes. GHSA-XRV3-JMCP-374J is fixed in 0.10.4, 0.9.7. Upgrade to this version or later.

Q: Is GHSA-XRV3-JMCP-374J exploitable, and should I be worried?

Whether GHSA-XRV3-JMCP-374J is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-XRV3-JMCP-374J is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-XRV3-JMCP-374J?

Upgrade: zerovec to 0.10.4 or later, zerovec to 0.9.7 or later.

Summary

zerovec incorrectly uses #[repr(packed)]

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.

Impact

GHSA-XRV3-JMCP-374J has a CVSS score of 6.2 (Medium). The vector is requires local access, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.10.4, 0.9.7); upgrading removes the vulnerable code path.

Affected versions

zerovec (>= 0.10.0, < 0.10.4) zerovec (< 0.9.7)

Security releases

zerovec → 0.10.4 (rust) zerovec → 0.9.7 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

zerovec to 0.10.4 or later; zerovec to 0.9.7 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-XRV3-JMCP-374J? GHSA-XRV3-JMCP-374J is a medium-severity security vulnerability in zerovec (rust), affecting versions >= 0.10.0, < 0.10.4. It is fixed in 0.10.4, 0.9.7.
How severe is GHSA-XRV3-JMCP-374J? GHSA-XRV3-JMCP-374J has a CVSS score of 6.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of zerovec are affected by GHSA-XRV3-JMCP-374J? zerovec (rust) versions >= 0.10.0, < 0.10.4 is affected.
Is there a fix for GHSA-XRV3-JMCP-374J? Yes. GHSA-XRV3-JMCP-374J is fixed in 0.10.4, 0.9.7. Upgrade to this version or later.
Is GHSA-XRV3-JMCP-374J exploitable, and should I be worried? Whether GHSA-XRV3-JMCP-374J is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-XRV3-JMCP-374J is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-XRV3-JMCP-374J?
- Upgrade zerovec to 0.10.4 or later
- Upgrade zerovec to 0.9.7 or later