Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀 crates.io
Not in CISA KEV

GHSA-g23h-7vf9-xc25 mimalloc

GHSA-g23h-7vf9-xc25 is a security vulnerability in mimalloc. A fix is available for mimalloc — see the affected versions and patch details below.

Mimalloc Can Allocate Memory with Bad Alignment

Also known asRUSTSEC-2022-0094
Published
Nov 12, 2024
Updated
Sep 10, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🦀mimalloc

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

This crate depended on a promise regarding alignments made by the author of the mimalloc allocator to avoid using aligned allocation functions where possible for performance reasons. Since then, the mimalloc allocator's logic changed, making it break this promise. This caused this crate to return memory with an incorrect alignment for some allocations, particularly those with large alignments. The flaw was fixed by always using the aligned allocation functions.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.iomimallocall versions0.1.39cargo update -p mimalloc --precise 0.1.39

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update mimalloc to 0.1.39 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g23h-7vf9-xc25 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

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

Tailored to GHSA-g23h-7vf9-xc25. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

This crate depended on a promise regarding alignments made by the author of the mimalloc allocator to avoid using aligned allocation functions where possible for performance reasons. Since then, the mimalloc allocator's logic changed, making it break this promise. This caused this crate to return memory with an incorrect alignment for some allocations, particularly those with large alignments. The flaw was fixed by always using the aligned allocation functions.
O3 Security · Impact-Aware SCA

Is GHSA-g23h-7vf9-xc25 in your dependencies?

O3 Security finds GHSA-g23h-7vf9-xc25 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-g23h-7vf9-xc25: mimalloc | O3 Security