CVE-2026-69148 mlflow CVE debrief

Who should care

MLflow users and administrators should assess exposure and verify access controls for model versioning and artifact access. Defenders should verify and restrict model version creation and artifact access. This vulnerability affects MLflow users and administrators who should assess exposure and verify access controls for model versioning and artifact access.

Why it matters

CVE-2026-69148 allows authenticated MLflow users to potentially read unauthorized files through the model's versioning feature; defenders should verify and restrict model version creation and artifact access.

• Potential unauthorized file access through MLflow's model versioning feature
• Need to verify and restrict model version creation and artifact access
• Possible data exposure for MLflow users with access to sensitive data

Technical summary

The CreateModelVersion function in MLflow's server/handlers.py file does not properly validate user input, allowing authenticated users to access unauthorized artifact directories and read files through the GET /model-versions/get-artifact endpoint. This issue is fixed in version 3.15.0. The vulnerability affects MLflow users and administrators who should assess exposure and verify access controls for model versioning and artifact access. Defenders should verify and restrict model version creation and artifact access.

Defensive priority

Authenticated users could potentially read unauthorized files through MLflow's model versioning feature; verify and restrict model version creation and artifact access.

Recommended defensive actions

• Verify model version creation and artifact access controls in MLflow
• Restrict CreateModelVersion function to prevent unauthorized access
• Update to MLflow version 3.15.0 or later
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review. MLflow users and administrators should assess exposure and verify access controls for model versioning and artifact access. Track
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability in MLflow's CreateModelVersion function, which allows authenticated users to access unauthorized artifact directories. The vulnerability has been fixed in MLflow version 3.15.0. Evidence is limited to public CVE and NVD records, and defenders should verify and restrict model version creation and artifact access.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.