CVE-2026-103009

High

Description

Authorization Bypass Through User-Controlled Key (CWE-639) in Elasticsearch can lead to Information Disclosure via a specially crafted cross-cluster search request that references an unauthorized shard identifier. Elasticsearch contains an authorization bypass weakness in its handling of cross-cluster search requests made through the Remote Cluster Security (RCS) 2.0 model. An authorization check validates a request against one identifying attribute of the target shard, while a separate, independently-supplied identifying attribute in the same request determines which shard is actually accessed. A holder of a cross-cluster API key authorized for one index can craft a request whose two identifying attributes refer to different indices, causing the request to be authorized against an index they can access while actually operating against a different, unauthorized index. This can expose that index's document contents, field mappings, and other metadata, and in limited cases allows modification of retention-lease state on the unauthorized index.

SeverityHigh
CVSS7.1
Exploit probability—
ProductElasticsearch
PublishedOct 6, 2026
First seenOct 6, 2026

How to fix

Update
  • elastic elasticsearch8.19.23, 9.4.8, 9.5.5 or later

Affected products

ProductAffected versionsFixed in
elastic elasticsearch8.13.0 ≤ v < 8.19.23, 9.0.0 ≤ v < 9.4.8, 9.5.0 ≤ v < 9.5.58.19.23, 9.4.8, 9.5.5

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.