VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

memmap2: vulnerability history, versions and safety

memmap2 is a package in the crates.io ecosystem. Vulert records 1 vulnerability for it across 35 releases, first recorded in Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 20 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all memmap2 vulnerabilities

Vulert verdict on memmap2 0.9.12 i

Updated on 23 Oct 2026

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

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 0.9.12 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 20 Jun 2026 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 658 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence Apache-2.0 OR MIT i

Version list, release dates, licence and dependants published by crates.io, refreshed 23 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 memmap2, 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.9.12 21 Oct 2026 none Apache-2.0 OR MIT — Details →
0.9.11 22 Jun 2026 none Apache-2.0 OR MIT — Details →
0.9.10 15 Feb 2026 U1 Apache-2.0 OR MIT Yes Details →
0.9.9 21 Oct 2025 U1 Apache-2.0 OR MIT Yes Details →
0.9.8 22 Aug 2025 U1 Apache-2.0 OR MIT Yes Details →
0.9.7 13 Jul 2025 U1 Apache-2.0 OR MIT Yes Details →
0.9.5 13 Sep 2024 U1 Apache-2.0 OR MIT Yes Details →
0.9.4 25 Jan 2024 U1 Apache-2.0 OR MIT Yes Details →
0.9.3 19 Dec 2023 U1 Apache-2.0 OR MIT Yes Details →
0.9.2 17 Dec 2023 U1 Apache-2.0 OR MIT Yes Details →
0.9.1 16 Dec 2023 U1 Apache-2.0 OR MIT Yes Details →
0.9.0 03 Oct 2023 U1 Apache-2.0 OR MIT Yes Details →
0.8.0 25 Sep 2023 U1 Apache-2.0 OR MIT Yes Details →
0.7.1 24 Jun 2023 U1 Apache-2.0 OR MIT Yes Details →
0.7.0 08 Jun 2023 U1 Apache-2.0 OR MIT Yes Details →
0.6.2 24 May 2023 U1 Apache-2.0 OR MIT Yes Details →
0.6.1 10 May 2023 U1 Apache-2.0 OR MIT Yes Details →
0.6.0 09 May 2023 U1 Apache-2.0 OR MIT Yes Details →
0.5.10 22 Feb 2023 U1 Apache-2.0 OR MIT Yes Details →
0.5.9 17 Feb 2023 U1 Apache-2.0 OR MIT Yes Details →
0.5.8 09 Nov 2022 U1 Apache-2.0 OR MIT Yes Details →
0.5.7 15 Aug 2022 U1 Apache-2.0 OR MIT Yes Details →
0.5.6 11 Aug 2022 U1 Apache-2.0 OR MIT Yes Details →
0.5.5 09 Jul 2022 U1 Apache-2.0 OR MIT Yes Details →
0.5.4 04 Jun 2022 U1 Apache-2.0 OR MIT Yes Details →
0.5.3 10 Feb 2022 U1 Apache-2.0 OR MIT Yes Details →
0.5.2 10 Jan 2022 U1 Apache-2.0 OR MIT Yes Details →
0.5.1 09 Jan 2022 U1 Apache-2.0 OR MIT Yes Details →
0.5.0 19 Sep 2021 U1 Apache-2.0 OR MIT Yes Details →
0.4.0 16 Sep 2021 U1 Apache-2.0 OR MIT Yes Details →
0.3.1 15 Aug 2021 U1 Apache-2.0 OR MIT Yes Details →
0.3.0 10 Jun 2021 U1 Apache-2.0 OR MIT Yes Details →
0.2.3 24 May 2021 U1 Apache-2.0 OR MIT Yes Details →
0.2.2 03 Apr 2021 U1 Apache-2.0 OR MIT Yes Details →
0.2.1 08 Feb 2021 U1 Apache-2.0 OR MIT Yes Details →
0.2.0 19 Dec 2020 U1 Apache-2.0 OR MIT Yes Details →
0.1.0 18 Jan 2020 U1 Apache-2.0 OR MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for memmap2

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Unchecked Pointer Offset Vulnerability in memmap2 Package N/A unrated 0.9.11 20 Jun 2026

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 memmap2

Is memmap2 safe to use?

Vulert records 1 vulnerabilities for memmap2 in crates.io: 0 critical, 0 high, 0 medium and 0 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 memmap2's Vulert package health score?

Vulert scores memmap2 78/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 memmap2 affected?

No. 0.9.12, 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.

How many vulnerabilities does memmap2 have?

1 vulnerability is recorded for memmap2 in the crates.io ecosystem: 0 critical, 0 high, 0 medium and 0 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 memmap2 vulnerabilities disclosed?

1 vulnerability was recorded for memmap2 in the last 12 months, and the oldest entry in this database dates to 20 Jun 2026. 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 memmap2 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 memmap2 for upcoming vulnerabilities?

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