How severe is GHSA-gq3w-7jj3-x7gr?

GHSA-gq3w-7jj3-x7gr has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-gq3w-7jj3-x7gr?

GHSA-gq3w-7jj3-x7gr affects the following packages: mlflow (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-gq3w-7jj3-x7gr?

Update mlflow to 3.8.0rc0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gq3w-7jj3-x7gr is resolved across your whole dependency graph.

How do I detect GHSA-gq3w-7jj3-x7gr 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-gq3w-7jj3-x7gr 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-gq3w-7jj3-x7gr?

O3 pinpoints whether GHSA-gq3w-7jj3-x7gr 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-gq3w-7jj3-x7gr actively exploited in the wild?

No public exploit code has been indexed for GHSA-gq3w-7jj3-x7gr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-gq3w-7jj3-x7gr published, and has it been updated?

GHSA-gq3w-7jj3-x7gr was published on February 21, 2026 and was last updated on June 29, 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

CRITICAL severity

GHSA-gq3w-7jj3-x7gr

CRITICALFix: mlflow/mlflow#19260

GHSA-gq3w-7jj3-x7gr is a critical-severity (CVSS 9.8) remote code execution vulnerability in mlflow. O3 Security confirms whether GHSA-gq3w-7jj3-x7gr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

MLflow Use of Default Password Authentication Bypass Vulnerability

Also known asCVE-2026-2635PYSEC-2026-421

Published

Feb 21, 2026

Updated

Jun 29, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jun 29, 2026 · OSV.dev, 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 allows remote attackers to bypass authentication on affected installations of MLflow. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the basic_auth.ini file. The file contains hard-coded default credentials. An attacker can leverage this vulnerability to bypass authentication and execute arbitrary code in the context of the administrator.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`mlflow`	all versions	3.8.0rc0

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 3.8.0rc0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gq3w-7jj3-x7gr 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-gq3w-7jj3-x7gr 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-gq3w-7jj3-x7gr. 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 allows remote attackers to bypass authentication on affected installations of MLflow. Authentication is not required to exploit this vulnerability. The specific flaw exists within the basic_auth.ini file. The file contains hard-coded default credentials. An attacker can leverage this vulnerability to bypass authentication and execute arbitrary code in the context of the administrator.

O3 Security · Impact-Aware SCA

Is GHSA-gq3w-7jj3-x7gr in your dependencies?

O3 detects GHSA-gq3w-7jj3-x7gr 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