Maxminddb: `Reader::open_mmap` unsoundly marks unsafe memmap operation as safe
Affects maxminddbSource GCVE Database
0
Severity
MediumRated Medium by Threat Radar's AI analysis
- Patch
- Available – fixed in 0.27.0
Data as of 21 Nov 2026, 03:53 UTC
What to do
Upgrade maxminddb to 0.27.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
crates.iomaxminddbpkg:cargo/maxminddbOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to maxminddb version 0.27 or later, where the Reader::open_mmap function is correctly marked and handled to ensure memory safety. No other mitigation steps are indicated.
Description
maxminddb versions prior to 0.27 unsafely marked the Reader::open_mmap function as safe despite it wrapping an inherently unsafe memory mapping operation. This could lead to undefined behavior if the underlying file is modified on disk while the memory map is active. The issue was fixed in version 0.27.
References
Community reviews
Loading reviews…