Elasticsearch can lead to information disclosure · Incorrect Authorization
Source GCVE Database
Not known to be exploited · CVSS 4.3 Medium.
Data as of 3 Nov 2026, 19:45 UTC
Thin evidence
One scorer or none| CNA (elastic) | CVSS 3.1 | 4.3 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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
Since this is a vulnerability in Elasticsearch and not a cloud service, users should monitor vendor advisories for remediation updates. Until a fix is available, review and limit user roles and permissions carefully to minimize exposure.
Description
A vulnerability in Elasticsearch allows an authenticated user with restricted index access to retrieve values from constant_keyword fields that their role should exclude. This occurs because some search and query features do not enforce field-level security restrictions on this field type, leading to potential information disclosure.