How severe is GHSA-fmxj-6h9g-6vw3?

GHSA-fmxj-6h9g-6vw3 has a CVSS score of 10/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-fmxj-6h9g-6vw3?

GHSA-fmxj-6h9g-6vw3 affects the following packages: mlflow (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-fmxj-6h9g-6vw3?

Update mlflow to 2.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fmxj-6h9g-6vw3 is resolved across your whole dependency graph.

How do I detect GHSA-fmxj-6h9g-6vw3 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mlflow. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-fmxj-6h9g-6vw3 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-fmxj-6h9g-6vw3?

O3 pinpoints whether GHSA-fmxj-6h9g-6vw3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-fmxj-6h9g-6vw3 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-fmxj-6h9g-6vw3, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What type of vulnerability is GHSA-fmxj-6h9g-6vw3?

GHSA-fmxj-6h9g-6vw3 is classified as CWE-36 (CWE-36). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for GHSA-fmxj-6h9g-6vw3?

A Nuclei detection template exists for GHSA-fmxj-6h9g-6vw3, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-fmxj-6h9g-6vw3 published, and has it been updated?

GHSA-fmxj-6h9g-6vw3 was published on July 19, 2023 and was last updated on April 10, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-fmxj-6h9g-6vw3

CRITICAL

GHSA-fmxj-6h9g-6vw3 is a critical-severity (CVSS 10) CWE-36 vulnerability in mlflow. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-fmxj-6h9g-6vw3 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

MLflow Path Traversal vulnerability

Also known asBIT-mlflow-2023-3765CVE-2023-3765PYSEC-2023-308

Published

Jul 19, 2023

Updated

Apr 10, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Blast Radius

1 pkg affected

🐍mlflow

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Absolute Path Traversal in GitHub repository mlflow/mlflow prior to 2.5.0.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`mlflow`	all versions	2.5.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Absolute Path Traversal in GitHub repository mlflow/mlflow prior to 2.5.…

huntr.devNVDJul 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mlflow. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update mlflow to 2.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fmxj-6h9g-6vw3 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-fmxj-6h9g-6vw3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-fmxj-6h9g-6vw3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Absolute Path Traversal in GitHub repository mlflow/mlflow prior to 2.5.0.

O3 Security · Impact-Aware SCA

Is GHSA-fmxj-6h9g-6vw3 in your dependencies?

O3 detects GHSA-fmxj-6h9g-6vw3 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works