Intel

AIKIDO-2026-373238

mlflow-oidc-auth is vulnerable to Improper Authentication

Improper Authentication Pre-CVE
Found by Aikido Intel before public disclosure or CVE publication.
Published Today

82

High Risk

This Affects:

PYTHONmlflow-oidc-auth
7.15.0 - 7.16.0
Fixed in 7.17.0
Are you affected? Scan for Free

TL;DR

The plugin validates OIDC bearer tokens against any provider in its multi-provider registry but keys the resulting identity on the username claim alone, without binding it to the provider that asserted it. A valid token from one configured provider whose username claim matches an account owned by a different provider is authenticated as that account, allowing cross-provider account takeover. When bearer group claims are trusted, a secondary provider whose token asserts a group named like the admin group also provisions the principal as an administrator, because no policy limits which providers may confer administrator rights. The fix binds identities to the asserting provider and adds a per-provider admin_source policy so only trusted providers can grant admin.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and your deployment configures more than one identity provider in the OIDC provider registry.

Background info

mlflow-oidc-auth is vulnerable to Improper Authentication in versions 7.15.0 - 7.16.0.

How to fix this

Upgrade the mlflow-oidc-auth library to the patch version.

Are You Affected?

Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.

Free. No credit card required.

Aikido Platform