VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

enum-map: vulnerability history, versions and safety

enum-map is a package in the crates.io ecosystem. Vulert records 3 vulnerabilities for it across 3 releases, from Feb 2022 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H1 U2
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 21 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all enum-map vulnerabilities

Vulert verdict on enum-map 3.1.0 i

Updated on 23 Oct 2026

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

Package health score 81/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

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

  • Current release 3.1.0 — unaffected i
  • Vulnerabilities on record 3 over 4 years · 1 in the last year i
  • Latest disclosure 21 Jul 2026 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 1 packages i
  • Last release 3 months ago 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 enum-map, 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
3.1.0 21 Jul 2026 none Apache-2.0 OR MIT — Details →
3.0.0 20 Jul 2026 none Apache-2.0 OR MIT — Details →
2.7.3 24 Nov 2023 none Apache-2.0 OR MIT — Details →
2.7.2 16 Nov 2023 none Apache-2.0 OR MIT — Details →
3.0.0-beta.2 08 Nov 2023 none Apache-2.0 OR MIT — Details →
2.7.1 08 Nov 2023 none Apache-2.0 OR MIT — Details →
3.0.0-beta.1 23 Oct 2023 none Apache-2.0 OR MIT — Details →
2.7.0 20 Oct 2023 none Apache-2.0 OR MIT — Details →
3.0.0-0.gat.0 23 Sep 2023 U1 Apache-2.0 OR MIT Yes Details →
2.6.3 10 Sep 2023 none Apache-2.0 OR MIT — Details →
2.6.2 07 Sep 2023 none Apache-2.0 OR MIT — Details →
2.6.1 01 Aug 2023 none Apache-2.0 OR MIT — Details →
2.6.0 30 Jun 2023 none Apache-2.0 OR MIT — Details →
2.5.0 14 Mar 2023 none Apache-2.0 OR MIT — Details →
2.4.2 17 Dec 2022 none Apache-2.0 OR MIT — Details →
2.4.1 28 Jul 2022 none Apache-2.0 OR MIT — Details →
2.4.0 15 Jun 2022 none Apache-2.0 OR MIT — Details →
2.3.0 29 May 2022 none Apache-2.0 OR MIT — Details →
2.2.0 20 May 2022 none Apache-2.0 OR MIT — Details →
2.1.0 24 Mar 2022 none Apache-2.0 OR MIT — Details →
2.0.3 26 Feb 2022 none Apache-2.0 OR MIT — Details →
0.6.6 18 Feb 2022 none Apache-2.0 OR MIT — Details →
0.6.5 18 Feb 2022 none Apache-2.0 OR MIT — Details →
2.0.2 17 Feb 2022 none Apache-2.0 OR MIT — Details →
2.0.1 27 Jan 2022 H1 U1 Apache-2.0 OR MIT Yes Details →
2.0.0 10 Jan 2022 none Apache-2.0 OR MIT — Details →
2.0.0-2 04 Jan 2022 H1 U1 Apache-2.0 OR MIT Yes Details →
2.0.0-1 01 Oct 2021 none Apache-2.0 OR MIT — Details →
1.1.1 16 May 2021 none Apache-2.0 OR MIT — Details →
1.1.0 04 May 2021 none Apache-2.0 OR MIT — Details →
1.0.0 28 Mar 2021 none Apache-2.0 OR MIT — Details →
0.6.4 27 Oct 2020 none Apache-2.0 OR MIT — Details →
0.6.3 08 Sep 2020 none Apache-2.0 OR MIT — Details →
0.6.2 20 Dec 2019 none Apache-2.0 OR MIT — Details →
0.6.1 04 Oct 2019 none Apache-2.0 OR MIT — Details →
0.6.0 29 Jul 2019 none Apache-2.0 OR MIT — Details →
0.5.0 18 Jan 2019 none Apache-2.0 OR MIT — Details →
0.4.1 11 Jun 2018 none Apache-2.0 OR MIT — Details →
0.3.2 11 Jun 2018 none Apache-2.0 OR MIT — Details →
0.2.36 11 Jun 2018 none Apache-2.0 OR MIT — Details →
0.2.35 06 Jun 2018 none Apache-2.0 OR MIT — Details →
0.3.1 06 Jun 2018 none Apache-2.0 OR MIT — Details →
0.4.0 06 Jun 2018 none Apache-2.0 OR MIT — Details →
0.3.0 05 Jun 2018 none Apache-2.0 OR MIT — Details →
0.2.34 05 Jun 2018 none Apache-2.0 OR MIT — Details →
0.2.33 05 Jun 2018 none Apache-2.0 OR MIT — Details →
0.2.32 05 Jun 2018 none Apache-2.0 OR MIT — Details →
0.2.31 22 May 2018 none Apache-2.0 OR MIT — Details →
0.2.30 18 May 2018 none Apache-2.0 OR MIT — Details →
0.2.29 20 Apr 2018 none Apache-2.0 OR MIT — Details →
0.2.28 09 Apr 2018 none Apache-2.0 OR MIT — Details →
0.2.27 30 Mar 2018 none Apache-2.0 OR MIT — Details →
0.2.26 30 Mar 2018 none Apache-2.0 OR MIT — Details →
0.2.25 30 Mar 2018 none Apache-2.0 OR MIT — Details →
0.2.24 17 Jan 2018 none Apache-2.0 OR MIT — Details →
0.2.23 30 Nov 2017 none Apache-2.0 OR MIT — Details →
0.2.22 18 Nov 2017 none Apache-2.0 OR MIT — Details →
0.2.21 06 Nov 2017 none Apache-2.0 OR MIT — Details →
0.2.20 15 Sep 2017 none Apache-2.0 OR MIT — Details →
0.2.19 11 Sep 2017 none Apache-2.0 OR MIT — Details →
0.2.18 06 Sep 2017 none Apache-2.0 OR MIT — Details →
0.2.17 02 Sep 2017 none Apache-2.0 OR MIT — Details →
0.2.16 01 Sep 2017 none Apache-2.0 OR MIT — Details →
0.2.15 30 Aug 2017 none Apache-2.0 OR MIT — Details →
0.2.14 29 Aug 2017 none Apache-2.0 OR MIT — Details →
0.2.13 27 Aug 2017 none Apache-2.0 OR MIT — Details →
0.2.12 26 Aug 2017 none Apache-2.0 OR MIT — Details →
0.2.11 26 Aug 2017 none Apache-2.0 OR MIT — Details →
0.2.10 26 Aug 2017 none Apache-2.0 OR MIT — Details →
0.2.9 26 Jul 2017 none Apache-2.0 OR MIT — Details →
0.2.8 07 Jun 2017 none Apache-2.0 OR MIT — Details →
0.2.7 04 Jun 2017 none Apache-2.0 OR MIT — Details →
0.2.6 19 May 2017 none Apache-2.0 OR MIT — Details →
0.2.5 18 May 2017 none Apache-2.0 OR MIT — Details →
0.2.4 18 May 2017 none Apache-2.0 OR MIT — Details →
0.2.3 18 May 2017 none Apache-2.0 OR MIT — Details →
0.2.2 18 May 2017 none Apache-2.0 OR MIT — Details →
0.2.1 18 May 2017 none Apache-2.0 OR MIT — Details →
0.2.0 17 May 2017 none Apache-2.0 OR MIT — Details →
0.1.2 17 May 2017 none Apache-2.0 OR MIT — Details →
0.1.1 16 May 2017 none Apache-2.0 OR MIT — Details →
0.1.0 16 May 2017 none Apache-2.0 OR MIT — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for enum-map

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-0010: enum-map Macro Uninitialized Type Arbitrary Code Execution N/A unrated 2.0.2 17 Feb 2022
Vulnerability in enum-map package: enum_map macro can cause UB when `Enum` trait is incorrectly implemented N/A high 2.0.2 16 Jun 2022
Type Confusion Vulnerability in enum-map Package: Enum Trait Implementation Flaw N/A unrated 3.1.0 21 Jul 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 enum-map

Is enum-map safe to use?

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

Vulert scores enum-map 81/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 enum-map affected?

No. 3.1.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 enum-map should I use?

3.1.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 enum-map have?

3 vulnerabilities are recorded for enum-map in the crates.io ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 2 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 enum-map vulnerabilities disclosed?

1 vulnerability was recorded for enum-map in the last 12 months, and the oldest entry in this database dates to 17 Feb 2022. 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 enum-map 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 enum-map for upcoming vulnerabilities?

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