Skip to main content
VulnerabilityPublished Updated

CVE-2025-37731: Elastic Elasticsearch · Improper Authentication

Affects Elastic ElasticsearchSource CVE Database V5

0

Not known to be exploited · CVSS 6.8 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Mavenorg.elasticsearch/elasticsearchpkg:maven/org.elasticsearch/elasticsearchOther threatsAffected
  • 7.0.0 – 9.2.0
4 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-37731, organizations should implement strict controls over their Certificate Authorities and certificate issuance processes to prevent unauthorized or malicious certificates from being trusted. Employ certificate revocation mechanisms such as CRLs or OCSP to promptly invalidate suspicious certificates. Enhance Elasticsearch PKI realm configurations to enforce strict client certificate validation, including checking certificate attributes and revocation status. Monitor authentication logs for unusual client certificate usage or repeated authentication failures that may indicate exploitation attempts. Network segmentation and limiting Elasticsearch access to trusted networks reduce exposure. Consider deploying additional authentication layers or multi-factor authentication where possible to complement PKI authentication. Stay alert for official patches or updates from Elastic and apply them promptly once available. Conduct regular security audits of PKI infrastructure and Elasticsearch configurations to identify and remediate weaknesses.

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.

References

Community reviews

Loading reviews…