cve.bz

CVE-2023-6974 lfprojects mlflow: SSRF

9.8 criticalExploit referenceEPSS 1.5%Fix available

Critical (9.8) in lfprojects mlflow. EPSS 1.5% estimated probability of exploitation activity in the next 30 days. Fixed in mlflow 2.9.2.

A malicious user could use this issue to access internal HTTP(s) servers and in the worst case (ie: aws instance) it could be abuse to get a remote code execution on the victim machine.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
1.5% (unchanged from 1.5% a week ago; 1.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 75th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
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-6974 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-6974?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-6974?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-6974 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-59v3-898r-qwhjPyPImlflow<2.9.22.9.2
PYSEC-2026-416PyPImlflow<2.9.22.9.2

Attack patterns (CAPEC)

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

References

Check your stackJSON