Skip to main content
Exploitation reportedNot in CISA KEV yetFix availableAwaiting NVD analysis

CVE-2026-115886

MLflow: SSRF on unauthenticated MLflow servers via third-party scorer kwargs in the scorer invoke, register, and GenAI evaluate endpoints

Exploitation reported by one source. First attested on 2026-10-29 by GCVE · previdian.

  • Published2026-10-23
  • Fixed in3.17.0
  • WeaknessCWE-470 · CWE-918

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. From 3.12.0rc0 until 3.17.0, the scorer invoke, register, and GenAI evaluate endpoints, including unauthenticated POST /ajax-api/3.0/mlflow/scorer/invoke, accept serialized third-party scorer data that Scorer.model_validate_json resolves using a module-path allowlist without constraining the selected class or its constructor arguments. When optional trulens and trulens-providers-litellm packages are installed, an attacker can select mlflow.genai.scorers.trulens, choose a model URI outside MLflow's native provider registry so execution uses the LiteLLM fallback, and supply api_base and api_key values that cause the server to send an outbound request to an attacker-chosen or internal host with attacker-controlled headers and body. The vulnerable deserialization occurs before a tracking-store lookup or job submission. This issue is fixed in version 3.17.0.

Timeline

dates in UTC
  1. 2026-10-2322:16CVE publishedNVD
  2. 2026-10-2912:20Listed as exploited by GCVEGCVE
  3. 2026-10-2912:20Exploitation first reportedGCVE

Observed activity

isMalicious corpus · updated 2026-11-02 03:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-115886?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-115886?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

OSV
mlflow
BranchAffectedFixed in
3.x≥ 3.12.0, < 3.17.03.17.0
mlflow
BranchAffectedFixed in
3.x≥ 3.12.0rc0, < 3.17.03.17.0

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • mlflow
    Affected
    • = >= 3.12.0rc0, < 3.17.0no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-10-23

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • nemo-gymChainguardall versions · fixed in 0.5.0_rc0_git20260729-r11
  • nemo-rl-cuda-13.0-mcoreChainguardall versions · fixed in 0.7.0-r17

Vendor advisories

  • CVE-2026-115886 Red Hat Product Security22 known affected

    mlflow: mlflow: Server-Side Request Forgery via insecure scorer deserialization

    rhoai/odh-mlflow-rhel9 as a component of Red Hat OpenShift AI (RHOAI) · rhoai/odh-pipeline-runtime-datascience-cpu-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI) · rhoai/odh-pipeline-runtime-pytorch-cuda-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI) · +19 more

Full record on NVD

Fix

  1. Update mlflow to 3.17.0
  2. No fix available, says the vendor Red Hat Product Security CVE-2026-115886 · 22 productsFix deferred

Detection

read 2026-11-01 22:43 UTC
Nuclei template
available
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Published
2026-10-23
Last Modified
2026-10-29
NVD status
Awaiting Analysis
GitHub Advisory
GHSA-2wqp-q3c6-ccj5

Frequently asked questions

What is CVE-2026-115886?

MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. From 3.12.0rc0 until 3.17.0, the scorer invoke, register, and GenAI evaluate endpoints, including unauthenticated POST /ajax-api/3.0/mlflow/scorer/invoke, accept serialized third-party scorer data that Scorer.model_validate_json resolves using a module-path allowlist without constraining the selected class or its constructor arguments. When optional trulens and trulens-providers-litellm packages are installed, an attacker can select mlflow.genai.scorers.trulens, choose a model URI outside MLflow's native provider registry so execution uses the LiteLLM fallback, and supply api_base and api_key values that cause the server to send an outbound request to an attacker-chosen or internal host with attacker-controlled headers and body. The vulnerable deserialization occurs before a tracking-store lookup or job submission. This issue is fixed in version 3.17.0.

Is CVE-2026-115886 actively exploited?

A proof-of-concept exploit exists for CVE-2026-115886, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2026-115886?

CVE-2026-115886 has a CVSS v3 base score of 6.5 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N.

Running mlflow? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record