GPU VulnDB

Database/AI/ML frameworks & serving

MLflow: unauthenticated arbitrary file read via prompt-tagged model version source path

CVE-2026-2614AI/ML frameworks & servingcurated

Impact

An unauthenticated caller who can reach the MLflow tracking server can register a model version whose source is any local filesystem path, then retrieve that path's contents through the artifact handler. On a GPU fleet the tracking server usually runs with broad read access to the shared experiment store and the service account credentials used to pull training data and push images, so this reads out registry tokens, cloud credential files and other tenants' artifacts, not just model blobs. MLflow is commonly exposed cluster-wide to every team that trains on the cluster, so "unauthenticated" here often means any pod on the network. Confidentiality only - no write or code execution is claimed in the record.

Who can reach it

Anyone who can send HTTP requests to the MLflow tracking server. No authentication required.

What to do

Upgrade MLflow to 3.10.0 and restart the tracking server; the model registry stays intact, so this is a service restart rather than a node action. Red Hat has shipped errata for OpenShift AI 3.3 and 3.4 (RHSA-2026:34456, RHSA-2026:37275, RHSA-2026:60520) - apply those if MLflow arrives via RHOAI. Until patched, put authentication or a network policy in front of the tracking server and treat any credential readable by the server process as exposed.

References

Related entries

All AI/ML frameworks & serving entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.