Elasticsearch can lead to information disclosure · Use of Cache Containing Sensitive Information
Source GCVE Database
Not known to be exploited · CVSS 4.2 Medium.
Data as of 3 Nov 2026, 19:45 UTC
Thin evidence
One scorer or none| CNA (elastic) | CVSS 3.1 | 4.2 |
|---|
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| ElasticElasticsearch | Affected
| 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.