CVE-2026-115298: Elasticsearch incorrect authorization in field-level security

CVE-2026-115298 · Severity: medium · CVSS 4.3 · Published 2026-11-03

Elasticsearch, a search and analytics engine used to index and query large volumes of data, has an access control flaw that allows authenticated users to view sensitive fields they should not have access to. An attacker with restricted credentials can bypass field-level security restrictions and retrieve values from constant_keyword fields that their role explicitly excludes, potentially exposing confidential data.

Technologies: Elasticsearch. Vendors: Elastic.

Quick answers

Is CVE-2026-115298 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-115298 being exploited in the wild.
How severe is CVE-2026-115298?
Medium severity, with a CVSS score of 4.3, published 3 November 2026.
Which products and versions are affected?
Elasticsearch 8.0.0 through 8.19.23, 9.0.0 through 9.4.8, 9.5.0 through 9.5.5.
Is there a fix for CVE-2026-115298?
Yes: fixed in Elasticsearch 8.19.24, 9.4.9, 9.5.6. Until then: For deployments that cannot upgrade immediately, do not rely on field-level security alone to hide constant_keyword values; instead, store sensitive constant_keyword data in indices that restricted users cannot access, or keep it out of indices subject to field-level security restrictions. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-115298 attacked?
It is attacked over the network.
Am I affected by CVE-2026-115298?
Check whether you run Elasticsearch at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: Elasticsearch 8.19.24, 9.4.9, 9.5.6

For deployments that cannot upgrade immediately, do not rely on field-level security alone to hide constant_keyword values; instead, store sensitive constant_keyword data in indices that restricted users cannot access, or keep it out of indices subject to field-level security restrictions.

Technical details

An incorrect authorization flaw (CWE-863) in Elasticsearch allows authenticated users to access constant_keyword fields despite field-level security (FLS) rules that should restrict them. Some search and query features do not properly enforce FLS restrictions on this field type, allowing an attacker with limited index access to retrieve excluded field values via standard queries. The vulnerability requires authentication and valid index access but only partial role restrictions.

Affected products

  • Elastic Elasticsearch 8.0.0 through 8.19.23, 9.0.0 through 9.4.8, 9.5.0 through 9.5.5

Timeline

  • 2026-11-03: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.