Vulnerability Database · Bitnami · Package report

minio: vulnerability history, versions and safety

minio is a package in the Bitnami ecosystem. Vulert records 27 vulnerabilities for it across 25 affected ranges, from Mar 2024 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
27 vulnerabilities recorded C3 H16 M7 L1
i
6 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
7 in the last 12 months

Most recent disclosure 13 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on minio i

Updated on 23 Oct 2026

Careful: 6 of the 27 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 27 vulnerabilities on record across 2 years, 7 in the last year.

What to do: Plan around the 6 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 27 over 2 years · 7 in the last year i
  • Latest disclosure 13 May 2026 i
  • Highest CVSS n/a i
  • With no published fix 6 i

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

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
from 2022.11.08 up to 2026.03.17 (exclusive) 1
up to 2026.03.17 (exclusive) 1
up to 2025.10.15 (exclusive) 1
from 2024.6.6 up to 2025.2.28 (exclusive) 1
from 2022.6.23 up to 2024.12.13 (exclusive) 1
up to 2024.5.27 (exclusive) 1
from 2024.1.31 up to 2024.2.4 (exclusive) 1
up to 2023.12.23 (exclusive) 1
up to 2023.03.20 (exclusive) 2
from 2019.12.17 up to 2023.03.20 (exclusive) 1
from 2020.12.23 up to 2023.03.13 (exclusive) 1
from 2020.04.10 up to 2023.02.17 (exclusive) 1
up to 2022.07.29 (exclusive) 1
from 2019.09.25 up to 2022.06.02 (exclusive) 1
from 2021.12.09 up to 2022.04.12 (exclusive) 1
up to 2021.12.27 (exclusive) 1
up to 2021.03.17 (exclusive) 1
up to 2021.03.04 (exclusive) 1
up to 2021.01.30 (exclusive) 1
up to 2020.04.23 (exclusive) 1
from 2023.05.18 onwards, no fix published yet 2
from 2021.10.10 onwards, no fix published yet 1
from 2024.03.30 onwards, no fix published yet 1
from 2018.08.18 onwards, no fix published yet 1
from 2022.07.24 onwards, no fix published yet 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 16
  • 2025 4
  • 2026 7

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

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 minio

Is minio safe to use?

Vulert records 27 vulnerabilities for minio in Bitnami: 3 critical, 16 high, 7 medium and 1 low. 6 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does minio have?

27 vulnerabilities are recorded for minio in the Bitnami ecosystem: 3 critical, 16 high, 7 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new minio vulnerabilities disclosed?

7 vulnerabilities were recorded for minio in the last 12 months, and the oldest entry in this database dates to 06 Mar 2024. 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 minio 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 minio for upcoming vulnerabilities?

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