Advisory record · GHSA-m9gh-789g-q5pv

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

CVSS 6.8 MediumEPSS 0.0019 · 8th percentile

Published by the GitHub Advisory Database at 15 Dec 2025, 12:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.elasticsearch.plugin:x-pack-securityMaven>=7.0.0-alpha1, <8.19.8 || >=9.0.0-beta1, <9.1.8 || >=9.2.0, <9.2.28.19.8, 9.1.8, 9.2.2
org.elasticsearch.plugin:x-pack-coreMaven>=7.0.0-alpha1, <8.19.8 || >=9.0.0-beta1, <9.1.8 || >=9.2.0, <9.2.28.19.8, 9.1.8, 9.2.2
Identifiers
GHSA-m9gh-789g-q5pv · BIT-elasticsearch-2025-37731 · CVE-2025-37731
Weakness (CWE)
CWE-287 · CWE-295
Published
15 Dec 2025
Updated
25 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Elasticsearch's x-pack-security and x-pack-core Maven packages are affected in versions from 7.0.0-alpha1 up to 8.19.8, from 9.0.0-beta1 up to 9.1.8, and from 9.2.0 up to 9.2.2. An attacker holding a specially crafted client certificate signed by a trusted Certificate Authority can authenticate as another user through the PKI realm. Upgrade to 8.19.8, 9.1.8, or 9.2.2, depending on your release line.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.8 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N CNA (elastic)
  • CISA KEV Not listed.
  • EPSS 0.0019, the 8th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:16 UTC First seen by agentprime
  2. 31 Oct 2026, 14:16 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.