What it is
CVE-2026-115886 is an unauthenticated vulnerability affecting mlflow. 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...
Vulnerability report
SSRF on unauthenticated MLflow servers Server-Side Request Forgery
Mlflow · >= 3.12.0rc0, < 3.17.0
Decision summary
Direct answers before the deeper technical record.
What it is
CVE-2026-115886 is an unauthenticated vulnerability affecting mlflow. 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...
Have exploitation attempts been observed?
Yes. Previdian sensors have observed 38 exploitation attempts, 7 unique attacker IPs, and 2 countries targeting CVE-2026-115886. First observed Oct 28, 2026; last observed Oct 29, 2026. Confidence is confirmed.
Who is affected?
mlflow >= 3.12.0rc0, < 3.17.0.
What should we do?
Patch immediately, validate internet-facing exposure, and monitor for matching requests.
Overview
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.
Exploitation evidence
Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.
Previdian
Previdian sensors observed exploitation attempts targeting this vulnerability.
Previdian sensor
Previdian sensors observed exploitation attempts targeting this vulnerability.
GitHub Advisory Database
Public scanner or PoC coverage increases practical exploitability.
Per-source evidence links for KEV attestations are available through the Previdian Pro API.
Learn about Pro API access| Source | Added |
|---|---|
| Previdian Sensors First | 2026-10-29 12:20 UTC |
Operational indicators for this CVE are listed under Detection.
Sensor telemetry
Previdian sensor observations are exploitation attempts targeting this vulnerability. They do not show that the target was vulnerable or that the attempt succeeded. The cards and chart show volume, unique attackers, and daily activity.
38
Attempts observed
7
Unique attacker IPs
2
Attacker countries
IN · US
4
Sensors observed
CVE-2026-115886 exploitation attempts over the last 7 days
Daily events observed by Previdian sensors
Updated 30 Oct 2026
First observed 28 Oct 2026 · Last observed 29 Oct 2026
Pro adds sensor region and window summaries. Enterprise adds raw IPs, paths, User-Agents, and payloads.
Detection
Make the evidence actionable in scanner, SOC, and edge-control workflows.
Request targets and User-Agents available in Pro. Callback host details available in Enterprise.
Nuclei template detected 29 Oct 2026.
View Nuclei template (opens in new tab)No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.
Learn about virtual patches →Attacker IP indicators observed · available in Pro and Enterprise.
Sensor-derived attacker IP indicators are available to Pro and Enterprise accounts under Detection and through the Pro API.
Learn about Pro API accessScanner and exploit-framework references linked to this CVE.
| Scanner | Reference | Detected |
|---|---|---|
| Nuclei | https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2026/CVE-2026-115886.yaml | 29 Oct 2026 |
Risk and context
CVSS v3.1
Potential damage if exploited. Separate from whether attackers are using it.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS
0.7%
Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.
Recent mention · Github Advisory Database (PIP)
Summary MLflow's tracking server exposes POST /ajax-api/3.0/mlflow/scorer/invoke with no authentication, and the handler reflectively instantiates an attacker-named class from attacker-supplied JSON with unconstrained constructor kwargs. With the optional trulens +...
Read full advisoryThese PoCs are unverified and could contain malware. Use at your own risk.
nuclei · Created Unknown
ghsa · Created Unknown · AI assessment 99%
MLflow: SSRF on unauthenticated MLflow servers via third-party scorer kwargs in the scorer invoke, register, and GenAI evaluate endpoints
Timeline
04:31 UTC
Scanner coverage available
03:26 UTC
Indicators of compromise recorded
03:26 UTC
Previdian sensors observed exploitation attempts targeting this vulnerability.
01:20 UTC
Pro and Enterprise Watch users had 5 days of early warning before Previdian KEV.
22:10 UTC
Public proof-of-concept code published
21:17 UTC
Vulnerability disclosed publicly
19:37 UTC
Identifier reserved by the CNA
Pro API
Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.
GET /api/v2/pro/kevs/CVE-2026-115886
Sample API response{
"cve_id": "CVE-2026-115886",
"confidence": "Confirmed",
"cvss_score": 6.5,
"cvss_estimated": false,
"epss_score": 0.00676,
"exploit_status": {
"exploited_in_the_wild": true,
"active_exploitation_observed": true
},
"sensor_telemetry": { "attempts": 38, "sensors": 4 }
}