CVE-2026-71211

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM 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(medium)
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
17%
KEV
Not listed

Published

August 5, 2026

Last Modified

August 26, 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.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
pipmlflow—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
mlflow3.13.0, 3.14.0, 3.15.0, 3.15.1, 3.15.2——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 96× 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.

Showing the most recent 100 of 169 total refreshes for this CVE.

  1. 2026-09-19 07:50 UTCEG score recompute
  2. 2026-09-19 07:50 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 17:56 UTCGHSA enrichment
  5. 2026-09-18 04:59 UTCEG score recompute
  6. 2026-09-18 04:59 UTCGHSA enrichment
  7. 2026-09-17 16:01 UTCGHSA enrichment
  8. 2026-09-17 01:08 UTCEG score recompute
  9. 2026-09-17 01:08 UTCGHSA enrichment
  10. 2026-09-16 14:08 UTCEPSS rescore
  11. 2026-09-16 05:27 UTCEG score recompute
  12. 2026-09-16 05:27 UTCGHSA enrichment
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-15 16:29 UTCEG score recompute
  15. 2026-09-15 16:29 UTCGHSA enrichment
  16. 2026-09-15 03:12 UTCEPSS rescore
  17. 2026-09-15 01:32 UTCGHSA enrichment
  18. 2026-09-14 07:30 UTCGHSA enrichment
  19. 2026-09-13 18:33 UTCEG score recompute
  20. 2026-09-13 18:33 UTCGHSA enrichment
  21. 2026-09-13 05:35 UTCGHSA enrichment
  22. 2026-09-12 16:37 UTCEG score recompute
  23. 2026-09-12 16:37 UTCGHSA enrichment
  24. 2026-09-12 15:02 UTCEPSS rescore
  25. 2026-09-12 03:40 UTCEG score recompute
Show 75 more
  1. 2026-09-12 03:40 UTCGHSA enrichment
  2. 2026-09-11 14:53 UTCEPSS rescore
  3. 2026-09-11 14:42 UTCEG score recompute
  4. 2026-09-11 14:42 UTCGHSA enrichment
  5. 2026-09-10 21:58 UTCEG score recompute
  6. 2026-09-10 21:58 UTCGHSA enrichment
  7. 2026-09-10 09:35 UTCEPSS rescore
  8. 2026-09-10 08:46 UTCGHSA enrichment
  9. 2026-09-09 19:24 UTCGHSA enrichment
  10. 2026-09-09 06:27 UTCEG score recompute
  11. 2026-09-09 06:27 UTCGHSA enrichment
  12. 2026-09-08 22:01 UTCEPSS rescore
  13. 2026-09-08 08:02 UTCGHSA enrichment
  14. 2026-09-07 18:24 UTCEG score recompute
  15. 2026-09-07 18:24 UTCGHSA enrichment
  16. 2026-09-06 20:30 UTCEG score recompute
  17. 2026-09-06 20:30 UTCGHSA enrichment
  18. 2026-09-06 13:48 UTCEPSS rescore
  19. 2026-09-06 07:28 UTCGHSA enrichment
  20. 2026-09-05 18:29 UTCEG score recompute
  21. 2026-09-05 18:28 UTCGHSA enrichment
  22. 2026-09-05 03:56 UTCEG score recompute
  23. 2026-09-05 03:56 UTCGHSA enrichment
  24. 2026-09-04 09:40 UTCEG score recompute
  25. 2026-09-04 09:39 UTCGHSA enrichment
  26. 2026-09-04 05:07 UTCEPSS rescore
  27. 2026-09-03 20:33 UTCGHSA enrichment
  28. 2026-09-03 07:03 UTCEG score recompute
  29. 2026-09-03 07:03 UTCGHSA enrichment
  30. 2026-09-02 14:12 UTCEPSS rescore
  31. 2026-09-02 09:42 UTCGHSA enrichment
  32. 2026-09-01 20:42 UTCEG score recompute
  33. 2026-09-01 20:42 UTCGHSA enrichment
  34. 2026-09-01 13:54 UTCEPSS rescore
  35. 2026-09-01 04:40 UTCEPSS rescore
  36. 2026-08-31 22:53 UTCGHSA enrichment
  37. 2026-08-30 23:26 UTCEG score recompute
  38. 2026-08-30 23:26 UTCGHSA enrichment
  39. 2026-08-30 19:17 UTCEPSS rescore
  40. 2026-08-30 10:29 UTCEG score recompute
  41. 2026-08-30 10:29 UTCGHSA enrichment
  42. 2026-08-30 01:22 UTCEPSS rescore
  43. 2026-08-29 21:31 UTCEG score recompute
  44. 2026-08-29 21:31 UTCGHSA enrichment
  45. 2026-08-28 21:42 UTCEPSS rescore
  46. 2026-08-27 21:09 UTCEG score recompute
  47. 2026-08-27 21:09 UTCGHSA enrichment
  48. 2026-08-27 08:12 UTCGHSA enrichment
  49. 2026-08-26 18:01 UTCEG score recompute
  50. 2026-08-26 18:01 UTCGHSA enrichment
  51. 2026-08-26 14:47 UTCEPSS rescore
  52. 2026-08-26 06:51 UTCGHSA enrichment
  53. 2026-08-25 17:53 UTCEG score recompute
  54. 2026-08-25 17:53 UTCGHSA enrichment
  55. 2026-08-25 13:49 UTCEPSS rescore
  56. 2026-08-25 04:55 UTCGHSA enrichment
  57. 2026-08-24 15:57 UTCEG score recompute
  58. 2026-08-24 15:57 UTCGHSA enrichment
  59. 2026-08-24 02:58 UTCGHSA enrichment
  60. 2026-08-23 13:52 UTCGHSA enrichment
  61. 2026-08-23 00:55 UTCEG score recompute
  62. 2026-08-23 00:55 UTCGHSA enrichment
  63. 2026-08-23 00:19 UTCEPSS rescore
  64. 2026-08-22 11:57 UTCEG score recompute
  65. 2026-08-22 11:57 UTCGHSA enrichment
  66. 2026-08-21 23:49 UTCEPSS rescore
  67. 2026-08-21 22:44 UTCGHSA enrichment
  68. 2026-08-21 09:46 UTCEG score recompute
  69. 2026-08-21 09:46 UTCGHSA enrichment
  70. 2026-08-20 22:56 UTCEPSS rescore
  71. 2026-08-20 20:49 UTCGHSA enrichment
  72. 2026-08-20 07:51 UTCGHSA enrichment
  73. 2026-08-19 18:54 UTCEG score recompute
  74. 2026-08-19 18:53 UTCGHSA enrichment
  75. 2026-08-19 17:04 UTCEPSS rescore

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 26, 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 82.7% 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

See which npm, PyPI, Go, and Maven packages are affected by 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