VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

miniz_oxide: vulnerability history, versions and safety

miniz_oxide is a package in the crates.io ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the crates.io ecosystem.

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 miniz_oxide vulnerabilities

Vulert verdict on miniz_oxide 0.9.1 i

Updated on 23 Oct 2026

Good news: 0.9.1, the version you would install today, has no known vulnerabilities.

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

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

  • Current release 0.9.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 145 packages i
  • Stars 258 i
  • OpenSSF scorecard 3/10 i
  • Last release 7 months ago i
  • Licence Apache-2.0 OR MIT OR Zlib 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 miniz_oxide, 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.1 13 Mar 2026 none Apache-2.0 OR MIT OR Zlib — Details →
0.9.0 12 Jan 2026 none Apache-2.0 OR MIT OR Zlib — Details →
0.8.9 09 Jun 2025 none Apache-2.0 OR MIT OR Zlib — Details →
0.8.8 08 Apr 2025 none Apache-2.0 OR MIT OR Zlib — Details →
0.8.7 03 Apr 2025 none Apache-2.0 OR MIT OR Zlib — Details →
0.8.6 03 Apr 2025 none Apache-2.0 OR MIT OR Zlib — Details →
0.8.5 21 Feb 2025 none Apache-2.0 OR MIT OR Zlib — Details →
0.8.4 11 Feb 2025 none Apache-2.0 OR MIT OR Zlib — Details →
0.8.3 13 Jan 2025 none Apache-2.0 OR MIT OR Zlib — Details →
0.8.2 17 Dec 2024 none Apache-2.0 OR MIT OR Zlib — Details →
0.8.1 17 Dec 2024 none Apache-2.0 OR MIT OR Zlib — Details →
0.8.0 08 Aug 2024 none Apache-2.0 OR MIT OR Zlib — Details →
0.7.4 18 Jun 2024 none Apache-2.0 OR MIT OR Zlib — Details →
0.7.3 17 May 2024 none Apache-2.0 OR MIT OR Zlib — Details →
0.7.2 03 Feb 2024 none Apache-2.0 OR MIT OR Zlib — Details →
0.7.1 02 Feb 2023 none Apache-2.0 OR MIT OR Zlib — Details →
0.6.4 01 Feb 2023 none Apache-2.0 OR MIT OR Zlib — Details →
0.6.3 01 Feb 2023 none Apache-2.0 OR MIT OR Zlib — Details →
0.7.0 01 Feb 2023 none Apache-2.0 OR MIT OR Zlib — Details →
0.6.2 04 Sep 2022 none Apache-2.0 OR MIT OR Zlib — Details →
0.5.4 04 Sep 2022 none Apache-2.0 OR MIT OR Zlib — Details →
0.6.1 25 Aug 2022 none Apache-2.0 OR MIT OR Zlib — Details →
0.6.0 21 Aug 2022 none Apache-2.0 OR MIT OR Zlib — Details →
0.5.3 30 May 2022 none Apache-2.0 OR MIT OR Zlib — Details →
0.5.1 11 Nov 2021 none Apache-2.0 OR MIT OR Zlib — Details →
0.5.0 04 Nov 2021 none Apache-2.0 OR MIT OR Zlib — Details →
0.4.4 25 Feb 2021 none Apache-2.0 OR MIT OR Zlib — Details →
0.4.3 07 Oct 2020 none Apache-2.0 OR MIT OR Zlib — Details →
0.4.2 13 Sep 2020 none MIT — Details →
0.4.1 22 Aug 2020 none MIT — Details →
0.4.0 28 Jun 2020 none MIT — Details →
0.3.7 10 Jun 2020 none MIT — Details →
0.3.6 03 Feb 2020 none MIT — Details →
0.3.5 27 Oct 2019 none MIT — Details →
0.3.4 26 Oct 2019 none MIT — Details →
0.3.3 05 Oct 2019 none MIT — Details →
0.3.2 11 Aug 2019 none MIT — Details →
0.3.1 07 Aug 2019 none MIT — Details →
0.3.0 22 Jul 2019 none MIT — Details →
0.2.3 21 Jul 2019 none MIT — Details →
0.2.2 01 Jul 2019 none MIT — Details →
0.2.1 23 Jan 2019 none MIT — Details →
0.2.0 16 Oct 2018 none MIT — Details →
0.1.3 23 Jun 2018 none MIT — Details →
0.1.2 09 Jan 2018 none MIT — Details →
0.1.1 28 Oct 2017 none MIT — Details →
0.1.0 10 Oct 2017 none MIT — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for miniz_oxide

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 miniz_oxide

Is miniz_oxide safe to use?

Vulert has no vulnerabilities on record for miniz_oxide in crates.io at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is miniz_oxide's Vulert package health score?

Vulert scores miniz_oxide 73/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 miniz_oxide affected?

No. 0.9.1, 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 miniz_oxide should I use?

0.9.1 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 miniz_oxide have?

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

How often are new miniz_oxide vulnerabilities disclosed?

0 vulnerabilities were recorded for miniz_oxide in the last 12 months. 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 miniz_oxide 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 miniz_oxide for upcoming vulnerabilities?

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