Skip to content

Hive has Double-free and Use After Free Vulnerabilities

Moderate severity GitHub Reviewed Published Feb 28, 2026 to the GitHub Advisory Database • Updated Feb 28, 2026

Package

hivex (Rust)

Affected versions

= 0.2.0

Patched versions

0.2.1

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.

References

Published to the GitHub Advisory Database Feb 28, 2026
Reviewed Feb 28, 2026
Last updated Feb 28, 2026

Severity

Moderate

EPSS score

Weaknesses

Double Free

The product calls free() twice on the same memory address. Learn more on MITRE.

Use After Free

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer. Learn more on MITRE.

CVE ID

No known CVE

GHSA ID

GHSA-j8cj-hw74-64jv

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.