Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-m9gh-789g-q5pv

MEDIUMFix: elastic/elasticsearch@cd97b85

GHSA-m9gh-789g-q5pv is a medium-severity (CVSS 6.8) Improper Authentication vulnerability in org.elasticsearch:elasticsearch. O3 Security confirms whether GHSA-m9gh-789g-q5pv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Elasticsearch PKI Realm Authentication Bypass Vulnerability Allows User Impersonation Through Crafted Client Certificates

Also known asBIT-elasticsearch-2025-37731CVE-2025-37731
Published
Dec 15, 2025
Updated
Feb 4, 2026
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed

Real-World Exposure

3 pkgs affected
org.elasticsearch:elasticsearchorg.elasticsearch:elasticsearchorg.elasticsearch:elasticsearch

Real-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

Improper Authentication in Elasticsearch PKI realm can lead to user impersonation via specially crafted client certificates. A malicious actor would need to have such a crafted client certificate signed by a legitimate, trusted Certificate Authority.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.elasticsearch:elasticsearch7.0.0-alpha1&&< 8.19.88.19.8
Mavenorg.elasticsearch:elasticsearch9.0.0-beta1&&< 9.1.89.1.8
Mavenorg.elasticsearch:elasticsearch9.2.0&&< 9.2.29.2.2

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.elasticsearch:elasticsearch. 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.

  2. Fix

    Update org.elasticsearch:elasticsearch to 8.19.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m9gh-789g-q5pv is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-m9gh-789g-q5pv 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-m9gh-789g-q5pv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Improper Authentication in Elasticsearch PKI realm can lead to user impersonation via specially crafted client certificates. A malicious actor would need to have such a crafted client certificate signed by a legitimate, trusted Certificate Authority.
O3 Security · Impact-Aware SCA

Is GHSA-m9gh-789g-q5pv in your dependencies?

O3 detects GHSA-m9gh-789g-q5pv across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.