CVE-2026-103009CWE-639

CVE-2026-103009

High · published October 7, 2026

CVSS v3.1
7.1
EPSS
0%
Percentile
13.1
In the wild
Unconfirmed
What it is

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.

The record
Technical detail
CVSS v3.1
7.1 · HIGH
Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
CVSS v4.0
Not supplied
EPSS
0.00231 · 13.1th percentile
Weakness
CWE-639 · Authorization Bypass Through User-Controlled Key
Published
2026-10-07T00:17Z
Affected products (3)
ProductVersionsFixed in
elastic/elasticsearch≥ 8.13.0, < 8.19.238.19.23
elastic/elasticsearch≥ 9.0.0, < 9.4.89.4.8
elastic/elasticsearch≥ 9.5.0, < 9.5.59.5.5
References (1)
EPSS history
Timeline
  • 08 OCT 03:27Z
    EPSS moved — → 0%
    epss
  • 06 OCT 19:31Z
    Authorization Bypass Through User-Controlled Key in Elasticsearch Leading to Information Disclosure
    cvelistv5