PoC Monitor
← All CVEs
CVE-2026-103009published 6 Oct 2026 19:31 UTCData: JSON · API

Elastic Elasticsearch

Authorization Bypass Through User-Controlled Key in Elasticsearch Leading to Information Disclosure

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.1high · scored by CNA · CWE-639
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Elastic Elasticsearch
  • >= 8.13.0, <= 8.19.22
  • >= 9.0.0, <= 9.4.7
  • >= 9.5.0, <= 9.5.4

Mitigation

The record names no fix. Check the vendor advisory below.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published6 Oct 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.