NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
CRITICAL severity

CVE-2023-6977 — mlflow

CRITICALFix: mlflow/mlflow@4bd7f27

CVE-2023-6977 is a critical-severity (CVSS 10) CWE-29 vulnerability in mlflow. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for mlflow — see the affected versions and patch details below.

Path Traversal: '\..\filename'

Also known asBIT-mlflow-2023-6977GHSA-qg8p-32gr-gh6xPYSEC-2026-1659
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
3.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk
0.00%33.3%66.7%100.0%83.0%3.9%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐍mlflow

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

Description

This vulnerability enables malicious users to read sensitive files on the server.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPImlflowall versions2.9.2pip install --upgrade 'mlflow==2.9.2'

Affected Products

1 product · 1 configurations
Application
mlflowlfprojects
≥ 1.0.0 && < 2.9.2
range
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.

This vulnerability enables malicious users to read sensitive files on th…

huntr.comNVDDec 2023

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. Fix

    Update mlflow to 2.9.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-6977 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How to detect CVE-2023-6977

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

nuclei -id cve-2023-6977 -u https://target
Template
Mlflow <2.8.0 - Local File Inclusion
Severity
high
Impact
Successful exploitation could allow an attacker to read sensitive files on the server.
Remediation
Upgrade Mlflow to version 2.9.2 or later to mitigate the vulnerability.

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

Frequently Asked Questions

This vulnerability enables malicious users to read sensitive files on the server.
O3 Security · Impact-Aware SCA

Is CVE-2023-6977 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2023-6977: mlflow — Fixed in 2.9.2