cve.bz

CVE-2023-6831 lfprojects mlflow: Path traversal

8.1 highExploit referenceEPSS 3.3%Fix available

High (8.1) in lfprojects mlflow. EPSS 3.3% estimated probability of exploitation activity in the next 30 days. Fixed in mlflow 2.9.2.

On this page
Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.9.2.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
EPSS
3.3% (unchanged from 3.3% a week ago; 3.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 89th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
CWE-29 Path Traversal: '\..\filename'
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-6831 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-6831?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-6831?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-6831 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
mlflow/mlflowbefore 2.9.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-554w-xh4j-8w64PyPImlflow<2.9.22.9.2
PYSEC-2023-253PyPImlflow<2.9.22.9.2

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON