What is GHSA-VGMH-MQM4-8J88?

GHSA-VGMH-MQM4-8J88 is a medium-severity use after free vulnerability in pared (rust), affecting versions < 0.4.0. It is fixed in 0.4.0. Memory is accessed after it has been freed, leading to undefined behavior in native code.

Which versions of pared are affected by GHSA-VGMH-MQM4-8J88?

pared (rust) versions < 0.4.0 is affected.

Is there a fix for GHSA-VGMH-MQM4-8J88?

Yes. GHSA-VGMH-MQM4-8J88 is fixed in 0.4.0. Upgrade to this version or later.

Is GHSA-VGMH-MQM4-8J88 exploitable, and should I be worried?

Whether GHSA-VGMH-MQM4-8J88 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-VGMH-MQM4-8J88 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.

GHSA-VGMH-MQM4-8J88 in pared

Q: Which versions of pared are affected by GHSA-VGMH-MQM4-8J88?

pared (rust) versions < 0.4.0 is affected.

Q: Is there a fix for GHSA-VGMH-MQM4-8J88?

Yes. GHSA-VGMH-MQM4-8J88 is fixed in 0.4.0. Upgrade to this version or later.

Q: Is GHSA-VGMH-MQM4-8J88 exploitable, and should I be worried?

Whether GHSA-VGMH-MQM4-8J88 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-VGMH-MQM4-8J88 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-VGMH-MQM4-8J88?

Upgrade pared to 0.4.0 or later.

Summary

pared Vulnerable to Use After Free in Parc and Prc Due to Missing Lifetime Constraints

Affected versions of this crate didn't provide sufficient lifetime constraints to conversion functions from alloc::sync::Arc and alloc::rc::Rc, which made it possible to create projections of these reference counted pointers. Unlike the original reference counted pointers, these projections could outlive original data's lifetimes.

This projected pointer could cause the original Arc's or Rc's Drop::drop to get called at a point where the original data was no longer valid, leading to a potential use after free.

The affected functions were

pared::prc::Prc::from_rc
pared::prc::Prc::project
pared::prc::Prc::try_from_rc
pared::sync::Parc::from_arc
pared::sync::Parc::project
pared::sync::Parc::try_from_arc

This flaw was fixed in 108f540ea8acb6073751a1aa386085c1cdc4fd1e by requiring that the type stored in the Arcs and Rcs passed to these functions contain T: 'static.

Impact

Memory is accessed after it has been freed, leading to undefined behavior in native code. Typical impact: memory corruption, crash, or potential code execution.

Affected versions

pared (< 0.4.0)

Security releases

pared → 0.4.0 (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 pared to 0.4.0 or later to resolve this vulnerability.

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

Frequently Asked Questions

What is GHSA-VGMH-MQM4-8J88? GHSA-VGMH-MQM4-8J88 is a medium-severity use after free vulnerability in pared (rust), affecting versions < 0.4.0. It is fixed in 0.4.0. Memory is accessed after it has been freed, leading to undefined behavior in native code.
Which versions of pared are affected by GHSA-VGMH-MQM4-8J88? pared (rust) versions < 0.4.0 is affected.
Is there a fix for GHSA-VGMH-MQM4-8J88? Yes. GHSA-VGMH-MQM4-8J88 is fixed in 0.4.0. Upgrade to this version or later.
Is GHSA-VGMH-MQM4-8J88 exploitable, and should I be worried? Whether GHSA-VGMH-MQM4-8J88 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-VGMH-MQM4-8J88 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-VGMH-MQM4-8J88? Upgrade pared to 0.4.0 or later.