Critical

MLflow Server-Side Request Forgery (SSRF)

  • Disclosed: 20.12.2023
  • Updated: 11.10.2026 12:20

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

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) mlflow < 2.9.2 2.9.2

References

CVSS score 9.8/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE)
CWE-918
Platform
Python (PyPI)
Package
mlflow
Disclosed
20.12.2023
Updated
11.10.2026 12:20

Sources and licenses

OSV / GitHub Advisory Database - GHSA-59v3-898r-qwhj - CC BY 4.0

OSV / GitHub Advisory Database - PYSEC-2026-416 - PyPA Advisory Database; CC BY 4.0

Vulnerability history: mlflow

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (82) in the archive
Total entries
82
First → latest
02.2022 09.2026
Without a fix
18
Exploited in attacks
1

Severity breakdown

  • Critical 20
  • High 48
  • Medium 13
  • Low 1

Disclosures per year

  1. 2022: 1
  2. 2023: 22
  3. 2024: 24
  4. 2025: 8
  5. 2026: 27
Severity:
  1. MLflow Server-Side Request Forgery (SSRF) this entry
    Critical · 9.8 CVE-2023-6974 < 2.9.2 2.9.2
  2. High · 7.1 CVE-2026-71211 >= 3.13.0, <= 3.15.2 no fix
  3. High · 8.1 CVE-2026-8147 >= 2.14.0rc0, < 3.13.0rc0 3.13.0rc0
  4. High · 7.0 CVE-2026-4137 >= 1.26.0, < 3.11.0 3.11.0
  5. Critical · 10.0 CVE-2025-15379 < 3.8.1 3.8.1
  6. Critical · 9.6 CVE-2025-15036 < 3.9.0rc0 3.9.0rc0
  7. High · 8.1 CVE-2025-15381 <= 3.8.1 no fix
  8. High · 8.1 CVE-2025-15031 < 3.9.0rc0 3.9.0rc0
  9. High · 7.5 CVE-2025-14287 < 3.8.0rc0 3.8.0rc0
  10. Critical · 9.8 CVE-2026-2635 < 3.8.0rc0 3.8.0rc0
  11. High · 7.0 CVE-2025-10279 < 3.4.0rc0 3.4.0rc0
  12. High · 8.1 CVE-2025-11200 < 2.22.0rc0 2.22.0rc0
  13. High · 8.1 CVE-2025-11201 < 2.22.4, >= 3.0.0rc0, < 3.0.0 2.22.4, 3.0.0
  14. High · 7.5 CVE-2024-8859 < 2.17.0rc0 2.17.0rc0
  15. High · 8.8 CVE-2024-37061 >= 1.11.0, <= 2.13.1 no fix
  16. High · 8.8 CVE-2024-37057 >= 2.0.0rc0, <= 2.14.1 no fix
  17. High · 8.8 CVE-2024-37058 >= 2.5.0, <= 2.14.1 no fix
  18. High · 8.8 CVE-2024-37060 >= 1.27.0, <= 2.14.1 no fix
  19. High · 8.8 CVE-2024-37059 >= 0.5.0, <= 3.4.0 no fix
  20. High · 8.8 CVE-2024-37054 >= 0.9.0, <= 2.14.1 no fix
  21. High · 8.8 CVE-2024-37052 >= 1.1.0, <= 2.14.1 no fix
  22. High · 8.8 CVE-2024-37055 >= 1.24.0, <= 2.14.1 no fix
  23. High · 8.8 CVE-2024-37056 >= 1.23.0, <= 2.14.1 no fix
  24. High · 8.8 CVE-2024-37053 >= 1.1.0, <= 2.14.1 no fix
Show more (20) Showing 41 of 68

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.