How severe is GHSA-qg8p-32gr-gh6x?

GHSA-qg8p-32gr-gh6x has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-qg8p-32gr-gh6x?

GHSA-qg8p-32gr-gh6x affects the following packages: mlflow (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-qg8p-32gr-gh6x?

Update mlflow to 2.9.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qg8p-32gr-gh6x is resolved across your whole dependency graph.

How do I detect GHSA-qg8p-32gr-gh6x 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-qg8p-32gr-gh6x 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-qg8p-32gr-gh6x?

O3 pinpoints whether GHSA-qg8p-32gr-gh6x 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-qg8p-32gr-gh6x actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-qg8p-32gr-gh6x, 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-qg8p-32gr-gh6x?

GHSA-qg8p-32gr-gh6x is classified as CWE-29 (CWE-29). 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-qg8p-32gr-gh6x?

A Nuclei detection template exists for GHSA-qg8p-32gr-gh6x, 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-qg8p-32gr-gh6x published, and has it been updated?

GHSA-qg8p-32gr-gh6x was published on December 20, 2023 and was last updated on July 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

HIGH severity

GHSA-qg8p-32gr-gh6x

HIGHFix: mlflow/mlflow@4bd7f27

GHSA-qg8p-32gr-gh6x is a high-severity (CVSS 7.5) CWE-29 vulnerability in mlflow. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-qg8p-32gr-gh6x is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

MLflow Local File Disclosure Vulnerability

Also known asBIT-mlflow-2023-6977CVE-2023-6977PYSEC-2026-1659

Published

Dec 20, 2023

Updated

Jul 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Jul 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

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

This vulnerability enables malicious users to read sensitive files on the server.

Affected Packages

1 total 1 fixed

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

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.

This vulnerability enables malicious users to read sensitive files on th…

huntr.comNVDDec 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.9.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qg8p-32gr-gh6x 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-qg8p-32gr-gh6x 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-qg8p-32gr-gh6x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

This vulnerability enables malicious users to read sensitive files on the server.

O3 Security · Impact-Aware SCA

Is GHSA-qg8p-32gr-gh6x in your dependencies?

O3 detects GHSA-qg8p-32gr-gh6x 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