CVE-2026-103009: Authorization Bypass Through User-Controlled Key (CWE-639) in Elasticsearch can lead to Information Disclosure via a specially crafted cross-cluster search…

PriorityP343high7.1CVSS 3.1

AVNACLPRLUINSUCHILAN

EPSS

0.23%

12.9th percentile

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.

Affected

7 ranges

Vendor	Product	Version range	Fixed in
elastic	elasticsearch	>= 8.13.0 < 8.19.23	8.19.23
elastic	elasticsearch	8.13.0 – 8.19.22	—
elastic	elasticsearch	>= 9.0.0 < 9.4.8	9.4.8
elastic	elasticsearch	9.0.0 – 9.4.7	—
elastic	elasticsearch	>= 9.5.0 < 9.5.5	9.5.5
elastic	elasticsearch	9.5.0 – 9.5.4	—
rhoai	odh-feature-server-rhel9	—	—

CVSS provenance

nvdv3.17.1HIGHCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

vendor_redhat7.1HIGH

Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.