CVE-2026-69146

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (30th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. From 3.13.0 until 3.15.0, LogInputs is absent from BEFORE_REQUEST_HANDLERS in the mlflow/server/auth package, allowing any authenticated user to call POST /api/2.0/mlflow/runs/log-inputs for another user's run_id and inject attacker-controlled DatasetInput records into the dataset_inputs lineage metadata without UPDATE permission. This issue is fixed in version 3.15.0.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100CISA SSVC

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
Severity65% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
30th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 17, 2026

Last Modified

September 18, 2026

Advisory Details (4)

Auto-updated Aug 17, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v3.15.0

Patch available: mlflow/mlflow v3.15.0

https://github.com/mlflow/mlflow/releases/tag/v3.15.0
github_commit

commit 5c34aec5669e (mlflow/mlflow)

Fix landed in mlflow/mlflow commit 5c34aec5669e — awaiting tagged release

https://github.com/mlflow/mlflow/commit/5c34aec5669e2386b38b5ee0855cd61174e27693
github_pr

Enforce update-run authorization on the LogInputs endpoint

Fix merged in mlflow/mlflow PR #24291 on 2026-07-06 — awaiting tagged release

https://github.com/mlflow/mlflow/pull/24291
github Patch Available🟡 PoC Available

LogInputs endpoint bypasses per-run UPDATE authorization in MLflow basic-auth · Advisory · mlflow/mlflow · GitHub

https://github.com/mlflow/mlflow/security/advisories/GHSA-3p64-6gvh-82v5

Vendor Advisories for CVE-2026-69146(1)

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

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
mlflow—
  • every version up to 3.15.0: fixed in 3.15.0
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-69146?
CVE-2026-69146 is a medium vulnerability published on August 17, 2026. MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. From 3.13.0 until 3.15.0, LogInputs is absent from BEFOREREQUESTHANDLERS in the mlflow/server/auth package, allowing any authenticated user to call POST /api/2.0/mlflow/runs/log-inputs…
When was CVE-2026-69146 disclosed?
CVE-2026-69146 was first published on August 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69146 actively exploited?
CVE-2026-69146 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69146?
CVE-2026-69146 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-69146?
A fix for CVE-2026-69146 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-69146 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-69146

Explore →

Is Your Infrastructure Affected by CVE-2026-69146?

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