Advisory record · GHSA-mj73-j457-8x9q

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

CVSS 4.0, no score published

Published by the GitHub Advisory Database at 2 Dec 2025, 00:29 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
maxminddbcrates.io>=0.11.0, <0.27.00.27.0
Identifiers
GHSA-mj73-j457-8x9q · RUSTSEC-2025-0132
Weakness (CWE)
CWE-915
Published
2 Dec 2025
Updated
11 Dec 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The maxminddb crate, versions 0.11.0 up to but not including 0.27.0, has a function `Reader::open_mmap` that is marked as safe even though it wraps an unsafe memory-mapping operation without the checks needed to guarantee safety. If the underlying database file is modified on disk while the memory map is active, undefined behaviour can result. Upgrade to maxminddb 0.27.0 or later.

Written 8 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
Not published None 4.0 CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 15:19 UTC First seen by agentprime
  2. 31 Oct 2026, 15:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.