VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

maxminddb: vulnerability history, versions and safety

maxminddb is a package in the crates.io ecosystem. Vulert records 2 vulnerabilities for it across 19 releases, from Nov 2025 to Dec 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded L1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 02 Dec 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all maxminddb vulnerabilities

Vulert verdict on maxminddb 0.32.0 i

Updated on 23 Oct 2026

Good news: 0.32.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 72/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Stay on 0.32.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.32.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 0.32.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 02 Dec 2025 i
  • Highest CVSS 2.7 i
  • With no published fix 0 i
  • Depended on by 2 packages i
  • Stars 279 i
  • OpenSSF scorecard 5/10 i
  • Last release 1 month ago i
  • Licence ISC i

Version list, release dates, licence and dependants published by crates.io, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for maxminddb, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.32.0 12 Sep 2026 none ISC — Details →
0.31.0 07 Sep 2026 none ISC — Details →
0.30.3 24 Aug 2026 none ISC — Details →
0.30.2 24 Aug 2026 none ISC — Details →
0.30.1 24 Aug 2026 none ISC — Details →
0.30.0 19 Jul 2026 none ISC — Details →
0.29.0 28 Jun 2026 none ISC — Details →
0.28.1 26 Apr 2026 none ISC — Details →
0.28.0 25 Apr 2026 none ISC — Details →
0.27.3 16 Feb 2026 none ISC — Details →
0.27.2 14 Feb 2026 none ISC — Details →
0.27.1 18 Dec 2025 none ISC — Details →
0.27.0 28 Nov 2025 none ISC — Details →
0.26.0 28 Mar 2025 L1 U1 ISC Yes Details →
0.25.0 16 Feb 2025 L1 U1 ISC Yes Details →
0.24.0 10 Jan 2024 L1 U1 ISC Yes Details →
0.23.0 03 Apr 2022 L1 U1 ISC Yes Details →
0.22.0 23 Mar 2022 L1 U1 ISC Yes Details →
0.21.0 20 Jul 2021 L1 U1 ISC Yes Details →
0.20.0 11 Jul 2021 L1 U1 ISC Yes Details →
0.19.0 25 Jun 2021 L1 U1 ISC Yes Details →
0.18.0 29 May 2021 L1 U1 ISC Yes Details →
0.17.3 29 May 2021 L1 U1 ISC Yes Details →
0.17.2 12 Feb 2021 L1 U1 ISC Yes Details →
0.17.1 04 Jan 2021 L1 U1 ISC Yes Details →
0.17.0 12 Dec 2020 L1 U1 ISC Yes Details →
0.16.0 05 Dec 2020 L1 U1 ISC Yes Details →
0.15.0 10 Oct 2020 L1 U1 ISC Yes Details →
0.14.0 07 Jun 2020 L1 U1 ISC Yes Details →
0.13.0 21 Jan 2019 L1 U1 ISC Yes Details →
0.12.0 09 Dec 2018 L1 U1 ISC Yes Details →
0.11.0 13 Nov 2018 L1 U1 ISC Yes Details →
0.10.0 08 Aug 2018 none ISC — Details →
0.9.0 17 Feb 2018 none ISC — Details →
0.8.1 02 Jul 2017 none ISC — Details →
0.8.0 29 Jun 2017 none ISC — Details →
0.7.2 16 Apr 2017 none ISC — Details →
0.7.1 14 Nov 2016 none ISC — Details →
0.7.0 15 May 2016 none ISC — Details →
0.6.2 24 Jan 2016 none ISC — Details →
0.6.1 11 Dec 2015 none ISC — Details →
0.6.0 26 Oct 2015 none ISC — Details →
0.5.5 05 Sep 2015 none ISC — Details →
0.5.4 09 Aug 2015 none ISC — Details →
0.5.3 20 May 2015 none ISC — Details →
0.5.2 16 May 2015 none Apache-2.0 — Details →
0.5.1 20 Apr 2015 none Apache-2.0 — Details →
0.5.0 19 Apr 2015 none Apache-2.0 — Details →
0.4.0 19 Apr 2015 none Apache-2.0 — Details →
0.3.0 04 Apr 2015 none Apache-2.0 — Details →
0.2.1 27 Mar 2015 none Apache-2.0 — Details →
0.2.0 24 Mar 2015 none Apache-2.0 — Details →
0.1.9 21 Mar 2015 none Apache-2.0 — Details →
0.1.8 28 Feb 2015 none Apache-2.0 — Details →
0.1.7 22 Feb 2015 none Apache-2.0 — Details →
0.1.6 14 Feb 2015 none Apache-2.0 — Details →
0.1.5 31 Jan 2015 none Apache-2.0 — Details →
0.1.4 24 Jan 2015 none Apache-2.0 — Details →
0.1.3 10 Jan 2015 none Apache-2.0 — Details →
0.1.2 04 Jan 2015 none Apache-2.0 — Details →
0.1.1 26 Dec 2014 none Apache-2.0 — Details →
0.1.0 22 Nov 2014 none Apache-2.0 — Details →
0.1.0-pre 22 Nov 2014 none — — Details →

All 63 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for maxminddb

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Memory Mapping Safety Issue in maxminddb Package 2.7 low 0.27.0 02 Dec 2025
Memory Safety Risk in maxminddb Package: Unsound Marking of open_mmap as Safe N/A unrated 0.27.0 28 Nov 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About maxminddb

Is maxminddb safe to use?

Vulert records 2 vulnerabilities for maxminddb in crates.io: 0 critical, 0 high, 0 medium and 1 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is maxminddb's Vulert package health score?

Vulert scores maxminddb 72/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of maxminddb affected?

No. 0.32.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of maxminddb should I use?

0.32.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does maxminddb have?

2 vulnerabilities are recorded for maxminddb in the crates.io ecosystem: 0 critical, 0 high, 0 medium and 1 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new maxminddb vulnerabilities disclosed?

2 vulnerabilities were recorded for maxminddb in the last 12 months, and the oldest entry in this database dates to 28 Nov 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of maxminddb are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor maxminddb for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the maxminddb version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.