How severe is GHSA-mj73-j457-8x9q?

No CVSS score has been assigned to GHSA-mj73-j457-8x9q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mj73-j457-8x9q?

GHSA-mj73-j457-8x9q affects the following packages: maxminddb (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-mj73-j457-8x9q?

Update maxminddb to 0.27.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mj73-j457-8x9q is resolved across your whole dependency graph.

How do I detect GHSA-mj73-j457-8x9q in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for maxminddb. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-mj73-j457-8x9q 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-mj73-j457-8x9q?

O3 pinpoints whether GHSA-mj73-j457-8x9q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-mj73-j457-8x9q actively exploited in the wild?

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

GHSA-mj73-j457-8x9q was published on December 2, 2025 and was last updated on December 11, 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

GHSA-mj73-j457-8x9q

maxminddb's `Reader::open_mmap` unsoundly marks unsafe memmap operation as safe

Also known asRUSTSEC-2025-0132

Published

Dec 2, 2025

Updated

Dec 11, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🦀maxminddb

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

maxminddb prior to version 0.27 declared Reader::open_mmap as safe despite wrapping an inherently unsafe memmap2 operation with no extra step done to guarantee safety. This could have led to undefined behaviour if the file were to be modified on disk while the memory map was still active.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`maxminddb`	≥ 0.11.0&&< 0.27.0	0.27.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for maxminddb. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update maxminddb to 0.27.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mj73-j457-8x9q 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 pinpoints whether GHSA-mj73-j457-8x9q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

Frequently Asked Questions

maxminddb prior to version 0.27 declared `Reader::open_mmap` as safe despite wrapping an inherently unsafe memmap2 operation with no extra step done to guarantee safety. This could have led to undefined behaviour if the file were to be modified on disk while the memory map was still active.

O3 Security · Impact-Aware SCA

Is GHSA-mj73-j457-8x9q in your dependencies?

O3 detects GHSA-mj73-j457-8x9q across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works