Skip to main content
CVE-2026-115298VulnerabilityPublished

Elasticsearch can lead to information disclosure · Incorrect Authorization

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-115298· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium.

Data as of 3 Nov 2026, 19:45 UTC

CVSS 3.1 base score
4.3Medium
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.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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.0.0 <=8.19.23
  • >=9.0.0 <=9.4.8
  • >=9.5.0 <=9.5.5
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.

References

Community reviews

Loading reviews…