VulertSecurity VulertSecurity

Vulnerability Database · Bitnami · Package report

mlflow: vulnerability history, versions and safety

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

i
79 vulnerabilities recorded C18 H47 M11 L3
i
6 with no fix published

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

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

Most recent disclosure 17 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mlflow vulnerabilities

Vulert verdict on mlflow i

Updated on 23 Oct 2026

Careful: 6 of the 79 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 79 vulnerabilities on record across 2 years, 27 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 79 over 2 years · 27 in the last year i
  • Latest disclosure 17 Sep 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
up to 3.15.0 (exclusive) 3
up to 3.14.0 (exclusive) 1
up to 3.13.0 (exclusive) 1
up to 3.11.1 (exclusive) 3
up to 3.11.0 (exclusive) 2
up to 3.10.1 (exclusive) 1
up to 3.10.0 (exclusive) 3
from 3.9.0 up to 3.10.0 (exclusive) 2
up to 3.9.0 (exclusive) 2
from 3.8.0 up to 3.9.0 (exclusive) 1
up to 3.7.0 (exclusive) 1
up to 3.5.0 (exclusive) 1
up to 3.4.0 (exclusive) 1
up to 3.1.0 (exclusive) 1
up to 3.0.0 (exclusive) 1
up to 2.21.1 (exclusive) 1
from 2.17.0 up to 2.20.1 (exclusive) 1
up to 2.19.0 (exclusive) 1
from 2.17.2 up to 2.18.0 (exclusive) 1
up to 2.16.0 (exclusive) 1
from 2.15.1 up to 2.16.0 (exclusive) 1
from 2.13.2 up to 2.14.0 (exclusive) 1
from 1.1.0 up to 2.13.2 (exclusive) 2
from 2.0.0 up to 2.13.2 (exclusive) 1
from 1.24.0 up to 2.13.2 (exclusive) 1
from 0.9.0 up to 2.13.2 (exclusive) 1
from 2.5.0 up to 2.13.2 (exclusive) 1
from 1.23.0 up to 2.13.2 (exclusive) 1
from 1.27.0 up to 2.13.2 (exclusive) 1
from 1.11.0 up to 2.13.2 (exclusive) 1
from 0.5.0 up to 2.13.2 (exclusive) 1
up to 2.12.2 (exclusive) 1
up to 2.12.1 (exclusive) 4
up to 2.11.3 (exclusive) 3
up to 2.10.0 (exclusive) 3
up to 2.9.2 (exclusive) 8
from 1.0.0 up to 2.9.2 (exclusive) 1
up to 2.9.1 (exclusive) 2
up to 2.8.2 (exclusive) 1
up to 2.8.1 (exclusive) 1
up to 2.6.0 (exclusive) 1
up to 2.5.0 (exclusive) 1
up to 2.3.1 (exclusive) 2
up to 2.2.2 (exclusive) 1
up to 2.2.1 (exclusive) 1
up to 2.0.1 (exclusive) 1
up to 1.23.1 (exclusive) 1
all releases, no fix published yet 4
all releases, no fix published yet 1
from 0.0.1 onwards, no fix published yet 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 38
  • 2025 16
  • 2026 25

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

03 Vulnerabilities

Recorded vulnerabilities for mlflow

The 5 most severe of 79 vulnerabilities recorded for this package

Search all 79 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Command Execution Vulnerability in Bitnami MLflow N/A critical 2.9.2 06 Mar 2024
Critical Vulnerability in mlflow N/A critical 2.9.2 06 Mar 2024
Arbitrary File Write Vulnerability in mlflow N/A high 2.9.2 06 Mar 2024
CVE-2026-79721: MLflow Code Execution Vulnerability in Versions 0.0.1 and Newer N/A high No fix published 17 Sep 2026
Sensitive File Disclosure in mlflow N/A high 2.9.2 06 Mar 2024

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 mlflow

Is mlflow safe to use?

Vulert records 79 vulnerabilities for mlflow in Bitnami: 18 critical, 47 high, 11 medium and 3 low. 6 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does mlflow have?

79 vulnerabilities are recorded for mlflow in the Bitnami ecosystem: 18 critical, 47 high, 11 medium and 3 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new mlflow vulnerabilities disclosed?

27 vulnerabilities were recorded for mlflow 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 mlflow 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 mlflow for upcoming vulnerabilities?

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