NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦 Bitnami
Not in CISA KEV

CVE-2023-6018 — mlflow

CVE-2023-6018 is a OS Command Injection vulnerability in mlflow. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asGHSA-5p3h-7fwh-92rcPYSEC-2026-417
Published
Updated
Affected
1 pkg
Patched
See advisory
Exploits
1 known
Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
47.9%probability of exploitation in next 30 days
High Risk0.00%
Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk
34.5%56.3%78.2%100.0%91.3%47.9%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected
📦mlflow

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Bitnami packages — download data is not available via public APIs for these ecosystems.

Description

An attacker can overwrite any file on the server hosting MLflow without any authentication.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦Bitnamimlflowall versionsNo fix

Affected Products

1 product · 1 configurations
Application
mlflowlfprojects
all
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mlflow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    The records we use list no patched version of mlflow for CVE-2023-6018. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

  3. Mitigate without a patch

    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

How to detect CVE-2023-6018

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2023-6018 -u https://target
Template
Mlflow - Arbitrary File Write
Severity
critical
Impact
Unauthenticated attackers can overwrite any file on the server hosting MLflow, potentially compromising system integrity and enabling remote code execution.
Remediation
Secure the MLflow instance by implementing authentication and access controls, and update to the latest patched version.

Template by ProjectDiscovery nuclei-templates (byt3bl33d3r), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

An attacker can overwrite any file on the server hosting MLflow without any authentication.
O3 Security · Impact-Aware SCA

Is CVE-2023-6018 in your dependencies?

Find it across Bitnami, including transitive dependencies.

CVE-2023-6018: mlflow