VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

enumflags2: vulnerability history, versions and safety

enumflags2 is a package in the crates.io ecosystem. Vulert records 2 vulnerabilities for it across 8 releases, first recorded in Apr 2023. 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 M1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all enumflags2 vulnerabilities

Vulert verdict on enumflags2 0.7.12 i

Updated on 23 Oct 2026

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

Package health score 80/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

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

  • Current release 0.7.12 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 24 Apr 2023 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 308 packages i
  • Stars 143 i
  • Last release 16 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 enumflags2, 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.7.12 09 Jun 2025 none Apache-2.0 OR MIT — Details →
0.7.11 17 Jan 2025 none Apache-2.0 OR MIT — Details →
0.7.10 07 Jun 2024 none Apache-2.0 OR MIT — Details →
0.7.9 12 Feb 2024 none Apache-2.0 OR MIT — Details →
0.7.8 13 Sep 2023 none Apache-2.0 OR MIT — Details →
0.7.7 17 Apr 2023 none Apache-2.0 OR MIT — Details →
0.7.6 01 Apr 2023 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.5 10 Apr 2022 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.4 24 Mar 2022 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.3 26 Dec 2021 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.2 14 Dec 2021 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.1 24 Feb 2021 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.0 24 Feb 2021 M1 U1 Apache-2.0 OR MIT Yes Details →
0.7.0-preview1 12 Aug 2020 M1 U1 Apache-2.0 OR MIT Yes Details →
0.6.4 21 Apr 2020 none Apache-2.0 OR MIT — Details →
0.6.3 11 Apr 2020 none Apache-2.0 OR MIT — Details →
0.6.2 16 Nov 2019 none Apache-2.0 OR MIT — Details →
0.6.1 24 Oct 2019 none MIT — Details →
0.6.0 04 Oct 2019 none MIT — Details →
0.5.2 02 May 2019 none MIT — Details →
0.5.1 02 Apr 2019 none MIT — Details →
0.5.0 29 Jan 2019 none MIT — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 2

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

03 Vulnerabilities

Recorded vulnerabilities for enumflags2

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-0035: enumflags2 - Adversarial Use of make_bitflags! Macro Can Cause Undefined Behavior N/A unrated 0.7.7 17 Apr 2023
Adversarial Use of `make_bitflags!` Macro in enumflags2 Package Can Cause Undefined Behavior N/A medium 0.7.7 24 Apr 2023

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 enumflags2

Is enumflags2 safe to use?

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

Vulert scores enumflags2 80/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 enumflags2 affected?

No. 0.7.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.

Which version of enumflags2 should I use?

0.7.12 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 enumflags2 have?

2 vulnerabilities are recorded for enumflags2 in the crates.io ecosystem: 0 critical, 0 high, 1 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 enumflags2 vulnerabilities disclosed?

0 vulnerabilities were recorded for enumflags2 in the last 12 months, and the oldest entry in this database dates to 17 Apr 2023. 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 enumflags2 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 enumflags2 for upcoming vulnerabilities?

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