Missing Authorization in Kibana Leading to Unauthorized Elasticsearch Index Data Exposure

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Elastic/Kibana (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Elastic/Kibana.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Sep 2, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 2, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 2, 2026

Sources and claim methodology

• Source referencediscuss.elastic.co

Related CVEs

• Observable Response Discrepancy in Kibana Leading to Cross-Space Information DisclosureSame elastic/kibana package
• Allocation of Resources Without Limits or Throttling in Kibana Leading to Denial of ServiceSame elastic/kibana package
• Improper Limitation of a Pathname to a Restricted Directory in Kibana Leading to Unauthorized Deletion of Privileged ResourcesSame elastic/kibana package
• Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in Kibana Leading to Unauthorized Resource DeletionSame elastic/kibana package
• Incorrect Authorization in Kibana Leading to Unauthorized Cross-Space Exposure of Machine Learning Job DataSame elastic/kibana package
• Stored Path Traversal in Kibana Leading to Unauthorized Deletion of Internal ResourcesSame elastic/kibana package