CVE-2023-1177

CRITICALNVD 9.39.3
EchelonGraph scoreHIGH confidence

Score elevated to 9.3 because EPSS predicts 93% probability of exploitation within the next 30 days (top 0.2% of all CVEs). NVD baseline CVSS 9.3 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Weaponized
9.3
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 69%
CISA-KEV: Not listedEPSS: 69%CVSS: 9.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.2.1.

CVSS v3
9.3
EG Score
9.3(high)
EPSS
99.3%
KEV
Not listed

Published

March 24, 2023

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated Jul 17, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
generic

huntr - The world's first bug bounty platform for AI/ML

https://huntr.dev/bounties/1fe8f21a-c438-4cba-9add-e8a5dab94e28
github_pr

Apply `validate_path_is_safe` to `path` and `artifact_path` for `/mlflow-artifacts/` endpoints

Fix merged in mlflow/mlflow PR #7891 on 2023-02-27 — awaiting tagged release

https://github.com/mlflow/mlflow/pull/7891/commits/7162a50c654792c21f3e4a160eb1a0e6a34f6e6e

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
mlflow0.0.1 ... 2.2.0 (69 versions)2.2.1

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:06 UTCEPSS rescore
  2. 2026-07-22 14:06 UTCEPSS rescore
  3. 2026-07-21 15:23 UTCEPSS rescore
  4. 2026-07-21 15:23 UTCEPSS rescore
  5. 2026-07-20 17:05 UTCEPSS rescore
  6. 2026-07-19 14:29 UTCEPSS rescore
  7. 2026-07-19 14:29 UTCEPSS rescore
  8. 2026-07-16 17:00 UTCEPSS rescore
  9. 2026-07-16 02:23 UTCOSV refresh
  10. 2026-07-15 16:56 UTCEPSS rescore
  11. 2026-07-15 16:56 UTCEPSS rescore
  12. 2026-07-13 22:28 UTCEPSS rescore
  13. 2026-07-13 22:28 UTCEPSS rescore
  14. 2026-07-13 06:11 UTCEPSS rescore
  15. 2026-07-13 06:11 UTCEPSS rescore
  16. 2026-07-12 05:44 UTCEPSS rescore
  17. 2026-07-11 08:25 UTCEPSS rescore
  18. 2026-07-11 08:25 UTCEPSS rescore
  19. 2026-07-09 19:08 UTCEPSS rescore
  20. 2026-07-08 15:13 UTCEPSS rescore
  21. 2026-07-07 13:44 UTCEPSS rescore
  22. 2026-07-04 06:29 UTCEPSS rescore
  23. 2026-07-01 15:04 UTCEPSS rescore
  24. 2026-06-29 14:04 UTCEPSS rescore
  25. 2026-06-28 14:06 UTCEPSS rescore
Show 29 more
  1. 2026-06-28 04:54 UTCEPSS rescore
  2. 2026-06-28 04:54 UTCEPSS rescore
  3. 2026-06-28 02:34 UTCOSV refresh
  4. 2026-06-25 13:48 UTCEPSS rescore
  5. 2026-06-25 13:48 UTCEPSS rescore
  6. 2026-06-24 14:03 UTCEPSS rescore
  7. 2026-06-24 14:03 UTCEPSS rescore
  8. 2026-06-23 21:31 UTCEPSS rescore
  9. 2026-06-23 21:31 UTCEPSS rescore
  10. 2026-06-18 17:51 UTCEPSS rescore
  11. 2026-06-18 17:51 UTCEPSS rescore
  12. 2026-06-17 17:51 UTCEPSS rescore
  13. 2026-06-17 17:51 UTCEPSS rescore
  14. 2026-06-16 17:51 UTCEPSS rescore
  15. 2026-06-16 17:51 UTCEPSS rescore
  16. 2026-06-15 17:47 UTCEPSS rescore
  17. 2026-06-12 23:10 UTCEPSS rescore
  18. 2026-06-12 23:10 UTCEPSS rescore
  19. 2026-06-11 13:58 UTCEPSS rescore
  20. 2026-06-11 13:58 UTCEPSS rescore
  21. 2026-06-10 13:17 UTCOSV refresh
  22. 2026-06-08 14:15 UTCEPSS rescore
  23. 2026-06-08 14:15 UTCEPSS rescore
  24. 2026-05-31 00:15 UTCEPSS rescore
  25. 2026-05-31 00:15 UTCEPSS rescore
  26. 2026-05-26 07:17 UTCEPSS rescore
  27. 2026-05-26 07:17 UTCEPSS rescore
  28. 2026-05-26 07:17 UTCEPSS rescore
  29. 2026-05-25 04:42 UTCEG score recompute

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2023/CVE-2023-1177.yaml
    First seen Jan 1, 2023

    Mlflow <2.2.1 - Local File Inclusion

    Open source ↗

Frequently asked(5)

What is CVE-2023-1177?
CVE-2023-1177 is a critical vulnerability published on March 24, 2023. Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.2.1.
When was CVE-2023-1177 disclosed?
CVE-2023-1177 was first published in the National Vulnerability Database on March 24, 2023, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-1177 actively exploited?
CVE-2023-1177 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-1177?
CVE-2023-1177 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2023-1177?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-1177, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-1177

Explore →

Is Your Infrastructure Affected by CVE-2023-1177?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.