GHSA-7mgx-gvjw-m3w3 is a high-severity (CVSS 7.5) Improper Authentication vulnerability in io.crate:crate. 1 public exploit reference exists, so weaponization risk is real. A fix is available for io.crate:crate — see the affected versions and patch details below.
CrateDB authentication bypass vulnerability
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- 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.
Exploitation and automatability from CISA’s SSVC triage for GHSA-7mgx-gvjw-m3w3.
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.
How urgent is this, really
GHSA-7mgx-gvjw-m3w3 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
io.crate:crate☕io.crate:crate☕io.crate:crate☕io.crate:crateReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
CrateDB 5.5.1 is contains an authentication bypass vulnerability in the Admin UI component. After configuring password authentication and_ Local_ In the case of an address, identity authentication can be bypassed by setting the X-Real IP request header to a specific value and accessing the Admin UI directly using the default user identity.(https://github.com/crate/crate/issues/15231)
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.crate:crate | all versions | 5.2.11io.crate:crate:5.2.11 |
| ☕Maven | io.crate:crate | ≥ 5.3.0&&< 5.3.8 | 5.3.8io.crate:crate:5.3.8 |
| ☕Maven | io.crate:crate | ≥ 5.4.0&&< 5.4.7 | 5.4.7io.crate:crate:5.4.7 |
| ☕Maven | io.crate:crate | ≥ 5.5.0&&< 5.5.2 | 5.5.2io.crate:crate:5.5.2 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.crate:crate, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.crate:crate to 5.2.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7mgx-gvjw-m3w3 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-7mgx-gvjw-m3w3 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-7mgx-gvjw-m3w3. 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-7mgx-gvjw-m3w3 in your dependencies?
O3 Security finds GHSA-7mgx-gvjw-m3w3 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.