Check out the latest research from IONIX: NEW! State of the WAF Report

New CVE Detected

CVE-2026-53995 – Path Traversal (Arbitrary Directory/File Write) – MLflow through 3.17.1

Be the first to know when new zero-days emerge:

Summary

CVE-2026-53995 is a path traversal vulnerability (CWE-22) in the FileStore tracking backend of MLflow 3.17.1 and earlier. An unauthenticated remote attacker can submit a crafted trace ID to write trace metadata files outside the intended directory. The CVE record lists a CVSS v4.0 score of 8.8 (High).

Technical details

  • Root cause: The POST /api/3.0/mlflow/traces endpoint accepts a trace ID containing traversal sequences, and the FileStore backend uses it unsanitized when building filesystem paths for trace metadata.
  • Trigger conditions: The MLflow server uses the FileStore tracking backend. FileStore is the default backend in versions before 3.7.0, so earlier deployments are exposed by default.
  • Attack vector: Network, no authentication or user interaction required.
  • Impact: Trace metadata files can be written outside the intended directory, limited by the permissions of the server process. The CVE record rates the impact as high on integrity and low on availability.

Affected software

  • MLflow versions 0 through 3.17.1 (FileStore tracking backend)

Severity

  • CVSS v4.0: 8.8 (High) – CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N
  • CVSS v3.1 (also listed in the CVE record): 8.2 (High) – CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

Mitigation and recommended actions

  • Immediate: the CVE record lists no fixed version. A fix has been proposed upstream (MLflow pull request 26842). Monitor MLflow releases and upgrade once a patched version is available.
  • Until a fix is available, do not expose MLflow servers to untrusted networks.
  • Put authentication in front of the server, such as a reverse proxy.
  • Consider a database-backed tracking store instead of FileStore.
  • Run the MLflow server process with minimal filesystem write permissions.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge