Skip to main content
CVE-2026-115710VulnerabilityPublished

Elasticsearch can lead to information disclosure · Use of Cache Containing Sensitive Information

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-115710· Medium 4.2

Not known to be exploited · CVSS 4.2 Medium.

Data as of 3 Nov 2026, 19:45 UTC

CVSS 3.1 base score
4.2Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (elastic)CVSS 3.14.2
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 3 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
ElasticElasticsearchAffected
  • >=8.9.0 <=8.19.23
  • >=9.0.0 <=9.4.8
  • >=9.5.0 <=9.5.5
Fixed in–

AI-suggested

Until a fix is available, consider restricting query patterns that could exploit this caching behavior or limit field-level security configurations to reduce exposure. Monitor vendor communications for updates on remediation.

Description

Elasticsearch has a vulnerability involving the use of cache containing sensitive information, which can lead to information disclosure and incorrect search results. Specifically, cached query results may be shared between users with different field-level security restrictions, allowing restricted users to infer data they should not access and causing incomplete results for users with full access. This issue arises only when a user with full access has recently run the same query on the same shard.

References

Community reviews

Loading reviews…