vulns.co
/
GKData.io MCP and API Buy me a coffee

Tachyon

MLflow: authorization must survive alternate resource interfaces

MLflow could authenticate a user yet allow restricted resource access when an interface lacked an authorization mapping. Tachyon's 2026 account of CVE-2025-14297 demonstrates restricted artifact reads and describes unauthorized writes and metadata access. The maintainer's change to the artifact interface supports the finding of a missing permission check.

Open the referenceResearch PaperReviewed 2026-10-03

How to use this reference

Document one actor/action/resource policy shared by all interfaces. Treat new helper interfaces as additions to the authorization model, and make missing enforcement fail closed. Compare remediation claims with the actual maintainer change: the reviewed artifact patch aligns alternate interface recognition with permission enforcement.

Before reading

  • Authentication versus object-level authorization
  • Applications with multiple interfaces to shared resources

Context and limits

  • The researcher limits exposure to self-hosted OSS basic-auth deployments with authenticated non-admin users; Databricks-managed MLflow is excluded.
  • Downstream code execution is a conditional modeled consequence in the article, not demonstrated production compromise or an automatic result of data access.
  • The article links a GraphQL commit that adds an authorization configuration switch; that commit alone does not establish the original GraphQL enforcement implementation or its complete patch chronology.
  • The maintainer artifact patch merged January 19, 2026, separately from February 3 publication. Exact affected-version and first-fixed-release bounds were not established from reviewed primary sources.
  • The underlying finding predates this article; 2026 labels the detailed educational publication. No bounty amount or independent exploit verification is claimed.

Sources

  1. CVE-2025-14297: MLflow Authorization BypassTachyon · reviewed 2026-10-03
  2. Enforce authorization on AJAX proxy artifact APIsMLflow · reviewed 2026-10-03
  3. Add an env var for controlling whether to enable GraphQL routes authorizationMLflow · reviewed 2026-10-03

Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software