Security Digest · Vulnerability record
CVE-2023-6014: MLflow authentication requirement bypass can allow a user to arbitrarily create an account
An attacker is able to arbitrarily create an account in MLflow bypassing any authentication requirment.
CVSS 9.1 Critical EPSS 1.2% · p67
Should you act?
Critical and remotely reachable
No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 1.2%, percentile 67: FIRST’s model estimates a 1.2% chance of exploitation activity in the next 30 days, higher than 67% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes
mlflow(PyPI) < 2.8.0, fixed in 2.8.0. Check your lockfile, including transitive dependencies.
What it is
An attacker is able to arbitrarily create an account in MLflow bypassing any authentication requirment.
From the GitHub advisory
An attacker is able to arbitrarily create an account in MLflow bypassing any authentication requirement.
Weakness type: CWE-598.
Product: mlflow (PyPI) · Assigned by: @huntr_ai · Published: 2023-11-16
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| PyPI | mlflow | < 2.8.0 | 2.8.0 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| mlflow | mlflow/mlflow | unspecified <= latest |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| @huntr_ai | 3.0 | 9.1 Critical | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 9.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Privileges required: none (no login)
- User interaction: none
- Scope: unchanged
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc, automatable yes, technical impact total.
- FIRST EPSS (model of 2026-10-21): 1.17% probability of exploitation activity in the next 30 days; percentile 67.
Timeline
- — CVE record published by @huntr_ai
- — GitHub-reviewed advisory GHSA-4qq5-mxxx-m6gg published (critical)
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-4qq5-mxxx-m6gg github.com
- CVE.org record CVE-2023-6014 cve.org
- NVD entry CVE-2023-6014 nvd.nist.gov
Other references from the CVE record and advisory
- huntr.com huntr.com
- github.com github.com
- github.com github.com
- github.com github.com
- github.com github.com