CVE-2023-3765Public exploitNetwork attack vector

Arbitrary file access via Windows path validation

Published Jul 19, 2023 · Updated Oct 24, 2024

Absolute path traversal in MLflow before 2.5.0 allows remote attackers to read, write, list, or delete files through artifact APIs. The validate_path_is_safe function fails to reject Windows drive-letter absolute paths that use forward slashes, so seven artifact endpoints pass attacker-chosen paths to storage operations. A reachable tracking server running on Windows is required; exploitation needs no authentication or user interaction and can expose, alter, or remove host-accessible files.

CVSS severity10.0
Critical
EPSS probability67.55%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Absolute path traversal in MLflow before 2.5.0 allows remote attackers to read, write, list, or delete files through artifact APIs. The validate_path_is_safe function fails to reject Windows drive-letter absolute paths that use forward slashes, so seven artifact endpoints pass attacker-chosen paths to storage operations. A reachable tracking server running on Windows is required; exploitation needs no authentication or user interaction and can expose, alter, or remove host-accessible files.

The record

CVE
CVE-2023-3765
Published
Jul 19, 2023
Updated
Oct 24, 2024
Vendor
MLflow Project
Product
MLflow
Classifications
CWE-36, T1005, T1083
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jul 19, 2023CVE publishedPublication date reported by the CVE source.
  2. Oct 24, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <2.5.0
  2. Affected versionversion=unspecified <2.5.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

MLflow Project · MLflowversion=0 <2.5.0; version=unspecified <2.5.0

Published CVSS scores

10.0huntr.devCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
10.0NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-36Absolute Path Traversal
T1005Data from Local System
T1083File and Directory Discovery

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo