{"id":"CVE-2026-103009","state":"PUBLISHED","title":"Authorization Bypass Through User-Controlled Key in Elasticsearch Leading to Information Disclosure","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.","publishedAt":"2026-10-06T19:31:53.261Z","updatedAt":"2026-10-06T19:52:13.370Z","severity":{"score":7.1,"label":"High","version":"3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N","source":"elastic"},"assigner":"elastic","products":["Elastic Elasticsearch"],"affected":[{"vendor":"Elastic","product":"Elasticsearch","defaultStatus":"unaffected","versions":[{"version":"8.13.0","status":"affected","lessThanOrEqual":"8.19.22","versionType":"semver"},{"version":"9.0.0","status":"affected","lessThanOrEqual":"9.4.7","versionType":"semver"},{"version":"9.5.0","status":"affected","lessThanOrEqual":"9.5.4","versionType":"semver"}]}],"references":["https://discuss.elastic.co/t/elasticsearch-8-19-23-9-4-8-9-5-5-security-update-esa-2026-199/390874"],"weaknesses":["CWE-639"],"ingestedAt":"2026-10-29T20:10:23.711Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2026/103xxx/CVE-2026-103009.json","commit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-103009","state":"PUBLISHED","datePublished":"2026-10-06T19:31:53.261Z","dateUpdated":"2026-10-06T19:52:13.370Z","assignerShortName":"elastic","assignerOrgId":"271b6943-45a9-4f3a-ab4e-976f3fa05b5a","dateReserved":"2026-09-29T20:57:38.467Z"},"containers":{"cna":{"title":"Authorization Bypass Through User-Controlled Key in Elasticsearch Leading to Information Disclosure","descriptions":[{"lang":"en","value":"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":[{"vendor":"Elastic","product":"Elasticsearch","defaultStatus":"unaffected","versions":[{"version":"8.13.0","status":"affected","lessThanOrEqual":"8.19.22","versionType":"semver"},{"version":"9.0.0","status":"affected","lessThanOrEqual":"9.4.7","versionType":"semver"},{"version":"9.5.0","status":"affected","lessThanOrEqual":"9.5.4","versionType":"semver"}]}],"references":[{"url":"https://discuss.elastic.co/t/elasticsearch-8-19-23-9-4-8-9-5-5-security-update-esa-2026-199/390874"}],"metrics":[{"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}],"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N","baseScore":7.1,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"LOW","availabilityImpact":"NONE"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-639","description":"CWE-639 Authorization Bypass Through User-Controlled Key","lang":"en","type":"CWE"}]}],"providerMetadata":{"shortName":"elastic","orgId":"271b6943-45a9-4f3a-ab4e-976f3fa05b5a","dateUpdated":"2026-10-06T19:31:53.261Z"},"source":{"discovery":"Elastic"},"x_generator":{"engine":"Elastic CVE Publisher 1.0.0"}},"adp":[{"title":"CISA ADP Vulnrichment","metrics":[{"other":{"type":"ssvc","content":{"timestamp":"2026-10-06T19:52:05.345727Z","id":"CVE-2026-103009","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}}],"providerMetadata":{"shortName":"CISA-ADP","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","dateUpdated":"2026-10-06T19:52:13.370Z"}}]}}}