GHSA-mhjq-8c7m-3f7p — milvus
Fix: milvus-io/milvus#45379GHSA-mhjq-8c7m-3f7p is a Improper Authentication vulnerability in github.com/milvus-io/milvus. A fix is available for github.com/milvus-io/milvus — see the affected versions and patch details below.
Milvus Proxy has a Critical Authentication Bypass Vulnerability
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-mhjq-8c7m-3f7p.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
github.com/milvus-io/milvus🐹github.com/milvus-io/milvus🐹github.com/milvus-io/milvus🐹github.com/milvus-io/milvusReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
What kind of vulnerability is it? Who is impacted? An unauthenticated attacker can exploit this vulnerability to bypass all authentication mechanisms in the Milvus Proxy component, gaining full administrative access to the Milvus cluster. This grants the attacker the ability to read, modify, or delete data, and to perform privileged administrative operations such as database or collection management. All users running affected Milvus versions are strongly advised to upgrade immediately.
Patches
Has the problem been patched? What versions should users upgrade to? This issue has been fixed in the following versions: • Milvus 2.4.24 • Milvus 2.5.21 • Milvus 2.6.5
Users should upgrade to these patched versions or later to mitigate the vulnerability.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading? If immediate upgrade is not possible, a temporary mitigation can be applied by removing the sourceID header from all incoming requests at the gateway, API gateway, or load balancer level before they reach the Milvus Proxy. This prevents attackers from exploiting the authentication bypass behavior.
References
Are there any links users can visit to find out more?
The following pull requests contain the fixes for the affected Milvus branches: • Fix for 2.4 branch • Fix for 2.5 branch • Fix for 2.6 branch
Special thanks to the Volcengine Milvus team at ByteDance([email protected]) for responsibly discovering, reporting, and coordinating the disclosure of this critical authentication bypass vulnerability with the Milvus maintainers.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/milvus-io/milvus | ≥ 0.10.4&&< 2.4.24 | 2.4.24go get github.com/milvus-io/milvus@v2.4.24 |
| 🐹Go | github.com/milvus-io/milvus | ≥ 2.5.0&&< 2.5.21 | 2.5.21go get github.com/milvus-io/milvus@v2.5.21 |
| 🐹Go | github.com/milvus-io/milvus | ≥ 2.6.0&&< 2.6.5 | 2.6.5go get github.com/milvus-io/milvus@v2.6.5 |
| 🐹Go | github.com/milvus-io/milvus | all versions | 0.10.3-0.20251107071934-6102f001a971go get github.com/milvus-io/milvus@v0.10.3-0.20251107071934-6102f001a971 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/milvus-io/milvus, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/milvus-io/milvus to 2.4.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mhjq-8c7m-3f7p 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mhjq-8c7m-3f7p can be triaged on real exposure rather than presence alone.
Tailored to GHSA-mhjq-8c7m-3f7p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-mhjq-8c7m-3f7p in your dependencies?
O3 Security finds GHSA-mhjq-8c7m-3f7p across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.