Vulnerability report

Exploitation Attempts Observed Confirmed Confidence Not in CISA KEV

CVE-2026-53995

mlflow < 3.18.0 Path Traversal

Mlflow · affected before 3.18.0

Severity
CVSS 8.8 · High
Confidence
Confirmed
Exploit status
Exploitation Attempts Observed in the Wild
EPSS
0.6%
First observed
14 Nov 2026
Last observed
14 Nov 2026

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2026-53995 is an unauthenticated vulnerability affecting mlflow.

Have exploitation attempts been observed?

Yes. Previdian sensors have observed 2 exploitation attempts, 1 unique attacker IP, and 1 country targeting CVE-2026-53995. First observed Nov 14, 2026. Confidence is confirmed.

Who is affected?

mlflow affected before 3.18.0.

What should we do?

Patch immediately, validate internet-facing exposure, and monitor for matching requests.

Overview

mlflow < 3.18.0 Path Traversal

MLflow before 3.18.0 contains a path traversal vulnerability in the FileStore tracking backend that allows unauthenticated attackers to control filesystem paths by submitting a crafted trace ID containing traversal sequences to the POST /api/3.0/mlflow/traces endpoint. Attackers can exploit FileStore.start_trace() to write trace_info.yaml, request_metadata, and tag files with attacker-controlled metadata outside the intended experiment trace directory, subject to the server process's filesystem permissions.

FileStore is the default tracking backend before MLflow 3.7.0 and opt-in thereafter (the default changed to a SQLite database), so deployments in the earlier part of the affected range are vulnerable without special configuration while later ones are affected only when FileStore is explicitly selected.

mlflow Affected
mlflow
Before 3.18.0
View vendor advisory (opens in new tab)
Published
19 Oct 2026
Exploitation Attempts Reported
14 Nov 2026
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
None

CVE References

Exploitation evidence

Evidence of exploitation attempts

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploitation Attempts Observed in the Wild

Previdian

Recorded 14 Nov 2026

Previdian sensors observed exploitation attempts targeting this vulnerability.

Exploitation Attempts Observed

Previdian sensor

First observed 14 Nov 2026

Previdian sensors observed exploitation attempts targeting this vulnerability.

Proof of concept available

CVE

Recorded 19 Oct 2026

Public scanner or PoC coverage increases practical exploitability.

Known exploited vulnerability sources

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-11-16 07:34 UTC

Operational indicators for this CVE are listed under Detection.

Sensor telemetry

Previdian Sensor Observations

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.

2

Attempts observed

1

Unique attacker IPs

1

Attacker countries

US

1

Sensors observed

CVE-2026-53995 exploitation attempts over the last 7 days

Daily events observed by Previdian sensors

Updated 17 Nov 2026

0
0
0
2
0
0
0
11 Nov 12 Nov 13 Nov 14 Nov 15 Nov 16 Nov 17 Nov

First observed 14 Nov 2026 · Last observed 14 Nov 2026

Pro adds sensor region and window summaries. Enterprise adds raw IPs, paths, User-Agents, and payloads.

Start 14-day Pro trial

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
1
1
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Scanner coverage

No scanner integrations recorded yet.

Virtual patch status

Previdian virtual patch guidance is available for this CVE.

AWS WAF Cloudflare ModSecurity

Attacker IP Indicators

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 access

Virtual Patch Detail

Compensating WAF rules for this CVE.

Available

Enterprise feature. Virtual patch rule content and deployable vendor exports (ModSecurity, Cloudflare, AWS WAF) are available to Previdian Enterprise users.

Risk and context

Severity, weaknesses, and research context

CVSS v4.0

8.8 High

Potential damage if exploited. Separate from whether attackers are using it.

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

EPSS

0.6%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

All CVSS Scores

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 8.2 High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

Potential Proof of Concepts

These PoCs are unverified and could contain malware. Use at your own risk.

Researcher Disclosure

cve · Created Unknown

Timeline

From disclosure to observed exploitation attempts

  1. 00:30 UTC

    Virtual patch available

    Compensating WAF rule available to block exploitation

  2. 23:26 UTC

    Indicator of compromise added

    Indicators of compromise recorded

  3. 23:26 UTC

    Observed by Previdian sensors

    Previdian sensors observed exploitation attempts targeting this vulnerability.

  4. 22:20 UTC

    Added to the Previdian watchlist

    Pro and Enterprise Watch users had 4 weeks of early warning before Previdian KEV.

  5. 21:30 UTC

    Public PoC available

    Public proof-of-concept code published

  6. 21:05 UTC

    CVE published

    Vulnerability disclosed publicly

  7. 16:07 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2026-53995

Sample API response
{
  "cve_id": "CVE-2026-53995",
  "confidence": "Confirmed",
  "cvss_score": 8.8,
  "cvss_estimated": false,
  "epss_score": 0.00625,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": true
  },
  "sensor_telemetry": { "attempts": 2, "sensors": 1 }
}