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.