CVE-2026-71211

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-05. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

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

MLflow's AI Gateway accepts an auth_config.api_base value when creating a gateway secret (mlflow/server/handlers.py, _create_gateway_secret) with no validation of scheme, host, or IP range; the value is stored verbatim. The gateway proxy endpoint (mlflow/server/gateway_api.py, raw_proxy) subsequently issues an HTTP request to that stored api_base plus a caller-supplied path and returns the full response body.

CVSS v3
7.1
EG Score
7.1(high)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

August 5, 2026

Last Modified

August 10, 2026

Advisory Details (1)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

mlflow/mlflow at v3.14.0 · mlflow/mlflow · GitHub

https://github.com/mlflow/mlflow/tree/v3.14.0/mlflow

Vendor Advisories for CVE-2026-71211(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 29× in last 7d / 75× 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-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 20:49 UTCGHSA enrichment
  3. 2026-08-20 07:51 UTCGHSA enrichment
  4. 2026-08-19 18:54 UTCEG score recompute
  5. 2026-08-19 18:53 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 04:44 UTCGHSA enrichment
  8. 2026-08-18 15:46 UTCEG score recompute
  9. 2026-08-18 15:46 UTCGHSA enrichment
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 01:50 UTCEG score recompute
  13. 2026-08-18 01:50 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 12:52 UTCGHSA enrichment
  16. 2026-08-16 23:55 UTCEG score recompute
  17. 2026-08-16 23:55 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 10:57 UTCEG score recompute
  21. 2026-08-16 10:57 UTCGHSA enrichment
  22. 2026-08-16 02:15 UTCEPSS rescore
  23. 2026-08-15 22:00 UTCGHSA enrichment
  24. 2026-08-15 09:02 UTCEG score recompute
  25. 2026-08-15 09:02 UTCGHSA enrichment
Show 50 more
  1. 2026-08-15 01:31 UTCEPSS rescore
  2. 2026-08-14 20:04 UTCGHSA enrichment
  3. 2026-08-14 07:07 UTCEG score recompute
  4. 2026-08-14 07:07 UTCGHSA enrichment
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-13 18:09 UTCGHSA enrichment
  7. 2026-08-13 05:11 UTCGHSA enrichment
  8. 2026-08-12 16:14 UTCEG score recompute
  9. 2026-08-12 16:14 UTCGHSA enrichment
  10. 2026-08-12 13:51 UTCEPSS rescore
  11. 2026-08-12 03:17 UTCGHSA enrichment
  12. 2026-08-11 14:19 UTCEG score recompute
  13. 2026-08-11 14:19 UTCGHSA enrichment
  14. 2026-08-11 01:22 UTCEG score recompute
  15. 2026-08-11 01:22 UTCGHSA enrichment
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 12:25 UTCEG score recompute
  18. 2026-08-10 12:25 UTCGHSA enrichment
  19. 2026-08-10 12:02 UTCGHSA enrichment
  20. 2026-08-10 11:22 UTCEG score recompute
  21. 2026-08-10 11:22 UTCGHSA enrichment
  22. 2026-08-10 11:06 UTCGHSA enrichment
  23. 2026-08-09 22:07 UTCEG score recompute
  24. 2026-08-09 22:07 UTCGHSA enrichment
  25. 2026-08-09 13:47 UTCEPSS rescore
  26. 2026-08-09 09:10 UTCGHSA enrichment
  27. 2026-08-08 20:13 UTCEG score recompute
  28. 2026-08-08 20:13 UTCGHSA enrichment
  29. 2026-08-08 16:37 UTCEPSS rescore
  30. 2026-08-08 07:15 UTCGHSA enrichment
  31. 2026-08-07 18:18 UTCEG score recompute
  32. 2026-08-07 18:18 UTCGHSA enrichment
  33. 2026-08-07 05:20 UTCGHSA enrichment
  34. 2026-08-06 16:22 UTCEG score recompute
  35. 2026-08-06 16:22 UTCGHSA enrichment
  36. 2026-08-06 13:47 UTCEPSS rescore
  37. 2026-08-06 03:24 UTCEG score recompute
  38. 2026-08-06 03:24 UTCGHSA enrichment
  39. 2026-08-05 19:17 UTCEPSS rescore
  40. 2026-08-05 19:17 UTCEPSS rescore
  41. 2026-08-05 14:27 UTCEG score recompute
  42. 2026-08-05 14:27 UTCGHSA enrichment
  43. 2026-08-05 13:47 UTCEG score recompute
  44. 2026-08-05 13:47 UTCGHSA enrichment
  45. 2026-08-05 13:10 UTCEG score recompute
  46. 2026-08-05 13:09 UTCGHSA enrichment
  47. 2026-08-05 08:20 UTCEG score recompute▼ 0.60
  48. 2026-08-05 08:20 UTCNVD updateCVSS v3 → 7.1
  49. 2026-08-05 07:22 UTCEG score recompute
  50. 2026-08-05 07:20 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-71211?
CVE-2026-71211 is a high vulnerability published on August 5, 2026. MLflow's AI Gateway accepts an authconfig.apibase value when creating a gateway secret (mlflow/server/handlers.py, creategatewaysecret) with no validation of scheme, host, or IP range; the value is stored verbatim. The gateway proxy endpoint (mlflow/server/gatewayapi.py, rawproxy) subsequently…
When was CVE-2026-71211 disclosed?
CVE-2026-71211 was first published in the National Vulnerability Database on August 5, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71211 actively exploited?
CVE-2026-71211 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.1% of all scored CVEs.
What is the CVSS score of CVE-2026-71211?
CVE-2026-71211 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-71211?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71211, 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

Explore the affected products and dependency analysis for CVE-2026-71211

Explore →

Is Your Infrastructure Affected by CVE-2026-71211?

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

Start Free Scan →Browse All CVEs