How severe is GHSA-j8cj-hw74-64jv?

No CVSS score has been assigned to GHSA-j8cj-hw74-64jv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j8cj-hw74-64jv?

GHSA-j8cj-hw74-64jv affects the following packages: hivex (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-j8cj-hw74-64jv?

Update hivex to 0.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j8cj-hw74-64jv is resolved across your whole dependency graph.

How do I detect GHSA-j8cj-hw74-64jv in my crates.io dependencies?

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

How do I mitigate GHSA-j8cj-hw74-64jv 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-j8cj-hw74-64jv?

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

Is GHSA-j8cj-hw74-64jv actively exploited in the wild?

No public exploit code has been indexed for GHSA-j8cj-hw74-64jv 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-j8cj-hw74-64jv published, and has it been updated?

GHSA-j8cj-hw74-64jv was published on February 28, 2026 and was last updated on March 1, 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

GHSA-j8cj-hw74-64jv — hivex

GHSA-j8cj-hw74-64jv is a security vulnerability in hivex. A fix is available for hivex — see the affected versions and patch details below.

Hive has Double-free and Use After Free Vulnerabilities

Also known asRUSTSEC-2026-0029

Published

Feb 28, 2026

Updated

Mar 1, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 1, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀hivex

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

Drop implementation for Hive did perform free, but so did Hive::close, which, at the end of the scope performed Drop, therefore triggering double-free.

Additionally, function Hive::from_handle was not marked as unsafe, making it, in combination with as_handle easy to clone and trigger double-free in safe code or triggering UB when using invalid pointer.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`hivex`	≥ 0.2.0&&< 0.2.1	0.2.1`cargo update -p hivex --precise 0.2.1`

Detection & mitigation playbook

Open-source dependency

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

Tailored to GHSA-j8cj-hw74-64jv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

`Drop` implementation for `Hive` did perform free, but so did `Hive::close`, which, at the end of the scope performed `Drop`, therefore triggering double-free. Additionally, function `Hive::from_handle` was not marked as unsafe, making it, in combination with `as_handle` easy to clone and trigger double-free in safe code or triggering UB when using invalid pointer.

O3 Security · Impact-Aware SCA

Is GHSA-j8cj-hw74-64jv in your dependencies?

O3 Security finds GHSA-j8cj-hw74-64jv 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