How severe is GHSA-vgmh-mqm4-8j88?

No CVSS score has been assigned to GHSA-vgmh-mqm4-8j88 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vgmh-mqm4-8j88?

GHSA-vgmh-mqm4-8j88 affects the following packages: pared (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-vgmh-mqm4-8j88?

Update pared to 0.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vgmh-mqm4-8j88 is resolved across your whole dependency graph.

How do I detect GHSA-vgmh-mqm4-8j88 in my crates.io dependencies?

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

How do I mitigate GHSA-vgmh-mqm4-8j88 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-vgmh-mqm4-8j88?

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

Is GHSA-vgmh-mqm4-8j88 actively exploited in the wild?

No public exploit code has been indexed for GHSA-vgmh-mqm4-8j88 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-vgmh-mqm4-8j88 published, and has it been updated?

GHSA-vgmh-mqm4-8j88 was published on March 24, 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

GHSA-vgmh-mqm4-8j88 — pared

Fix: radekvit/pared@108f540

GHSA-vgmh-mqm4-8j88 is a security vulnerability in pared. A fix is available for pared — see the affected versions and patch details below.

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

Also known asRUSTSEC-2025-0016

Published

Mar 24, 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

🦀pared

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

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.

Affected Packages

1 total 1 fixed

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

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pared, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pared to 0.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vgmh-mqm4-8j88 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-vgmh-mqm4-8j88 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-vgmh-mqm4-8j88. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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::P

O3 Security · Impact-Aware SCA

Is GHSA-vgmh-mqm4-8j88 in your dependencies?

O3 Security finds GHSA-vgmh-mqm4-8j88 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