MLflow: CreateModelVersion source validation does not check READ permission on referenced run_id

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

EPSS

• CVE-2026-69148: 0.37% estimated exploitation activity in the next 30 days; percentile 30.81 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The validatesourcerun and validatesourcemodel functions in mlflow/server/handlers.py verify that a model version source path is within the artifact directory of a specified run or logged model, but do not check whether the caller has READ permission on that run or model. An authenticated MLflow user can therefore reference another user's runid in CreateModelVersion, creating a model version whose artifact URI points at the victim's artifact directory. If the calling user has MANAGE permission on the registered model (which they do after creation), they can then read arbitrary files from the victim's artifact directory via GET /model-versions/get-artifact, bypassing the experiment-level READ permission gate on GET /get-artifact. Details POST /api/2.0/mlflow/model-versions/create is protected: the caller must have UPDATE permission on the registered model. However, the source/runid validation performed inside validatesourcerun only verifies path containment, not caller…

Published by the source

17 Aug 2026, 21:59 UTC

Last modified by the source

17 Aug 2026, 21:59 UTC

Source last checked

26 Oct 2026, 13:01 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-gqch-g4w5-7qcw

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-69148

Advisory: MLflow: CreateModelVersion source validation does not check READ permission on referenced run_id
IDs: CVE-2026-69148, GHSA-gqch-g4w5-7qcw
Record: https://patchnext.com/advisories/cve-2026-69148 (revision 1, source checked 26 Oct 2026, 13:01 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mlflow 3.15.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm mlflow: affected < 3.15.0; fixed in 3.15.0

## Suggested inspection (read-only)
- `npm ls mlflow --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mlflow.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gqch-g4w5-7qcw (GitHub-reviewed advisory GHSA-gqch-g4w5-7qcw lists affected ranges: npm mlflow >=0 <3.15.0)

Commands are suggestions: review each one before running it.