GHSA-hxp5-8pgq-mgv9 is a medium-severity (CVSS 5.9) CWE-295 vulnerability in org.apache.calcite:calcite-core. O3 Security confirms whether GHSA-hxp5-8pgq-mgv9 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Missing Authentication for Critical Function in Apache Calcite
Real-World Exposure
org.apache.calcite:calcite-core☕org.apache.calcite:calcite-druid☕org.apache.calcite:calcite-splunkReal-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
"HttpUtils#getURLConnection method disables explicitly hostname verification for HTTPS connections making clients vulnerable to man-in-the-middle attacks. Calcite uses this method internally to connect with Druid and Splunk so information leakage may happen when using the respective Calcite adapters. The method itself is in a utility class so people may use it to create vulnerable HTTPS connections for other applications. From Apache Calcite 1.26 onwards, the hostname verification will be performed using the default JVM truststore."
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.calcite:calcite-core | all versions | 1.26.0 |
| ☕Maven | org.apache.calcite:calcite-druid | all versions | 1.26.0 |
| ☕Maven | org.apache.calcite:calcite-splunk | all versions | 1.26.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.calcite:calcite-core. 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 org.apache.calcite:calcite-core to 1.26.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hxp5-8pgq-mgv9 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-hxp5-8pgq-mgv9 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-hxp5-8pgq-mgv9. 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-hxp5-8pgq-mgv9 in your dependencies?
O3 detects GHSA-hxp5-8pgq-mgv9 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.