{"schema":"threatline.record/2","record":{"id":"CVE-2026-103009","aliases":[],"summary":"Authorization Bypass Through User-Controlled Key in Elasticsearch Leading to Information Disclosure","details":"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.","categories":["Databases"],"product":"Elasticsearch","vendor":"Elastic","ecosystem":null,"affected_ranges":[{"source":"CVE List","source_url":"https://www.cve.org/CVERecord?id=CVE-2026-103009","source_modified_at":"2026-10-06T19:52:13.370Z","fetched_at":"2026-10-23T18:52:38.922436Z","product":"Elasticsearch","vendor":"Elastic","versions":[{"status":"affected","versionType":"semver","version":"8.13.0","lessThanOrEqual":"8.19.22"},{"status":"affected","versionType":"semver","version":"9.0.0","lessThanOrEqual":"9.4.7"},{"status":"affected","versionType":"semver","version":"9.5.0","lessThanOrEqual":"9.5.4"}],"defaultStatus":"unaffected"}],"fixed_versions":[],"cvss":7.1,"severity":"High","kev":{"listed":false},"epss":{"probability":0.00231,"percentile":0.13168,"score_date":"2026-10-23"},"published_at":"2026-10-06T19:31:53.261Z","modified_at":"2026-10-06T19:52:13.370Z","provenance":[{"source":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-103009","fetched_at":"2026-10-23T18:52:38.922436Z","source_modified_at":"2026-10-06T19:52:13.370Z"},{"source":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-103009","fetched_at":"2026-10-23T18:42:43.628194Z","source_modified_at":"2026-10-23"}],"sources":["CVE List","EPSS"],"references":[{"source":"CVE List","url":"https://discuss.elastic.co/t/elasticsearch-8-19-23-9-4-8-9-5-5-security-update-esa-2026-199/390874"}],"locations":[],"motoko_assessment":{"status":"requires_architecture_review","automatic_remediation":false},"cve_state":"PUBLISHED","cvss_source":"CVE List","ssvc":{"exploitation":"none","automatable":"no","technical_impact":"partial","assessed_at":"2026-10-06T19:52:05.345727Z"},"classification":{"method":"product-first software-layer rules","rules_version":"2.1","matched_on":"product","confidence":"heuristic","reviewed":false},"change_timestamp":"2026-10-06T19:52:13.370Z","content_hash":"7bebf9a2211e018a6a4ea6e6df5fa93a578221f56d4968f9a913a05aa8abc985"}}