# CVE-2025-37731: x-pack Auth Bypass — Fixed in 8.19.8 ☕ ☕ Maven Not in CISA KEV MEDIUM severity # CVE-2025-37731 — x-pack-security MEDIUM [Fix: elastic/elasticsearch@cd97b85](https://github.com/elastic/elasticsearch/commit/cd97b8566bf56e628070021300784cb9cee0286f) CVE-2025-37731 is a medium-severity (CVSS 6.8) Improper Authentication vulnerability in org.elasticsearch.plugin:x-pack-security. A fix is available for org.elasticsearch.plugin:x-pack-security — see the affected versions and patch details below. Elasticsearch Improper Authentication Also known asBIT-elasticsearch-2025-37731[GHSA-m9gh-789g-q5pv](/vulnerability/GHSA-m9gh-789g-q5pv) Published Dec 15, 2025 Updated Oct 28, 2026 Affected 6 pkgs Patched 6 / 6 Exploits None indexed Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS) ## Exploitation Status ### No confirmed exploitation observed yet - 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 CVE-2025-37731. ## EPSS Exploitation Probability [via FIRST.org ↗](https://www.first.org/epss/) 0.2%probability of exploitation in next 30 days Lower Risk0.00% Lower risk than most CVEs9th percentile — riskier than 9% of all scored CVEsHighest risk 0.00%0.23%0.46%0.69%0.1%0.2%May 26Sep 26Nov 26 Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/). ## How urgent is this, really ## Where this sits among everything scored ## Real-World Exposure 6 pkgs affected ☕`org.elasticsearch.plugin:x-pack-security`☕`org.elasticsearch.plugin:x-pack-security`☕`org.elasticsearch.plugin:x-pack-security`☕`org.elasticsearch.plugin:x-pack-core`☕`org.elasticsearch.plugin:x-pack-core`☕`org.elasticsearch.plugin:x-pack-core` 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 6 total 6 fixed Ecosystem Package Vulnerable range Fix ☕Maven `org.elasticsearch.plugin:x-pack-security` ≥ 7.0.0-alpha1&&< 8.19.8 8.19.8`org.elasticsearch.plugin:x-pack-security:8.19.8` ☕Maven `org.elasticsearch.plugin:x-pack-security` ≥ 9.0.0-beta1&&< 9.1.8 9.1.8`org.elasticsearch.plugin:x-pack-security:9.1.8` ☕Maven `org.elasticsearch.plugin:x-pack-security` ≥ 9.2.0&&< 9.2.2 9.2.2`org.elasticsearch.plugin:x-pack-security:9.2.2` ☕Maven `org.elasticsearch.plugin:x-pack-core` ≥ 7.0.0-alpha1&&< 8.19.8 8.19.8`org.elasticsearch.plugin:x-pack-core:8.19.8` ☕Maven `org.elasticsearch.plugin:x-pack-core` ≥ 9.0.0-beta1&&< 9.1.8 9.1.8`org.elasticsearch.plugin:x-pack-core:9.1.8` ☕Maven `org.elasticsearch.plugin:x-pack-core` ≥ 9.2.0&&< 9.2.2 9.2.2`org.elasticsearch.plugin:x-pack-core:9.2.2` ## Affected Products 1 product · 4 configurations Application `elasticsearch`elastic ≥ 9.2.0 && ≤ 7.17.29 range ## 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.plugin:x-pack-security, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version. 2. ### Fix Update org.elasticsearch.plugin:x-pack-security to 8.19.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-37731 is resolved across your whole dependency graph. 3. ### Workarounds Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used. ## Fixing This On Your OS If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project. Red HatModerate This vulnerability is rated Moderate for Red Hat because it allows user impersonation in Elasticsearch PKI realm. Exploitation requires a malicious actor to possess a specially crafted client certificate signed by a legitimate, trusted Certificate Authority. This impacts Elasticsearch deployments configured with PKI… Workaround published by Red Hat > To reduce the risk of exploitation, ensure that the Certificate Authority (CA) used for the Elasticsearch PKI realm is highly secured and has robust controls in place to prevent the signing of unauthorized client certificates. Additionally, restrict network access to the Elasticsearch instance to only trusted clients and networks, for example, by configuring firewall rules to limit inbound connections to the Elasticsearch port. Source: [Red Hat security advisory for CVE-2025-37731](https://access.redhat.com/security/cve/cve-2025-37731) (CC BY 4.0) ## 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 CVE-2025-37731 in your dependencies? Find it across Maven, including transitive dependencies. [Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)