{"id":"CVE-2026-103009","aliases":["BIT-elasticsearch-2026-103009"],"summary":"Authorization Bypass Through User-Controlled Key in Elasticsearch Leading to Information Disclosure","published_at":"2026-10-06T19:31:53.261Z","modified_at":"2026-10-31T07:20:40Z","products":[{"slug":"elasticsearch","name":"Elasticsearch / Kibana","category":"monitoring"}],"rating":{"severity":"high","score":7.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N","attack_path":"internet_authenticated","user_interaction":false,"malicious":false,"red_hat":"Important","vendor_ratings":[{"source":"Red Hat","rating":"Important"}]},"fix_available":true,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"epss":{"score":0.0024399999529123306,"percentile":0.15723000466823578,"date":"2026-11-18T00:00:00Z"},"priority":8.1,"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.","affected_stack":[{"ecosystem":"Bitnami","package":"elasticsearch","purl":"pkg:bitnami/elasticsearch","ranges":[{"type":"SEMVER","events":[{"introduced":"8.13.0"},{"fixed":"8.19.23"},{"introduced":"9.0.0"},{"fixed":"9.4.8"},{"introduced":"9.5.0"},{"fixed":"9.5.5"}]}],"fixed":["8.19.23","9.4.8","9.5.5"],"provider":"osv","source":"BIT-elasticsearch-2026-103009","relation":"self"},{"ecosystem":"CVE","package":"Elastic/Elasticsearch","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"8.13.0"},{"last_affected":"8.19.22"}]},{"type":"ECOSYSTEM","events":[{"introduced":"9.0.0"},{"last_affected":"9.4.7"}]},{"type":"ECOSYSTEM","events":[{"introduced":"9.5.0"},{"last_affected":"9.5.4"}]}],"provider":"cvelistv5","source":"CVE-2026-103009","relation":"self"}],"affected_other":[],"product_status":[{"vendor":"Red Hat","product":"Red Hat OpenShift AI (RHOAI)","cpe":"cpe:/a:redhat:openshift_ai","status":"affected","packages":["rhoai/odh-feature-server-rhel9"],"package_count":1,"fixed":[],"advisories":[],"note":"Fix deferred","provider":"redhat-vex","source":"CVE-2026-103009"},{"vendor":"Red Hat","product":"Red Hat Quay 3","cpe":"cpe:/a:redhat:quay:3","status":"not_affected","packages":["quay/quay-rhel8","quay/quay-rhel9"],"package_count":2,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2026-103009"}],"records":[{"provider":"csaf-bsi","source_id":"WID-SEC-W-2026-3784","relation":"upstream","url":"https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-3784","license":"TLP:CLEAR, mirroring permitted","published_at":"2026-10-06T22:00:00Z","modified_at":"2026-10-13T22:00:00Z","summary":"Elasticsearch: Mehrere Schwachstellen","details":"Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Elasticsearch ausnutzen, um Administratorrechte zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder Denial-of-Service-Zustände auszulösen.\n\nElasticsearch ist eine Open Source, verteilte Echtzeit-Suche und Analyse-Engine.","severity":[{"type":"BSI","score":"mittel","source":"WID-SEC-W-2026-3784"}],"affected":[],"product_status":[],"references":[{"type":"WEB","url":"https://wid.cert-bund.de/.well-known/csaf/white/2026/wid-sec-w-2026-3784.json"},{"type":"WEB","url":"https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-3784"},{"type":"WEB","url":"https://discuss.elastic.co/t/elasticsearch-8-19-19-9-3-8-9-4-4-security-update-esa-2026-188/390861"},{"type":"WEB","url":"https://discuss.elastic.co/t/elasticsearch-8-19-21-9-4-6-9-5-2-security-update-esa-2026-196/390870"},{"type":"WEB","url":"https://discuss.elastic.co/t/elasticsearch-8-19-22-9-4-7-9-5-4-security-update-esa-2026-197/390871"},{"type":"WEB","url":"https://discuss.elastic.co/t/elasticsearch-8-19-22-9-4-8-and-9-5-5-security-update-esa-2026-189/390862"},{"type":"WEB","url":"https://discuss.elastic.co/t/elasticsearch-8-19-23-9-4-8-9-5-5-security-update-esa-2026-185/390859"},{"type":"WEB","url":"https://discuss.elastic.co/t/elasticsearch-8-19-23-9-4-8-9-5-5-security-update-esa-2026-195/390869"},{"type":"WEB","url":"https://discuss.elastic.co/t/elasticsearch-8-19-23-9-4-8-9-5-5-security-update-esa-2026-198/390872"},{"type":"WEB","url":"https://discuss.elastic.co/t/elasticsearch-8-19-23-9-4-8-9-5-5-security-update-esa-2026-199/390874"},{"type":"WEB","url":"https://discuss.elastic.co/t/elasticsearch-9-4-7-9-5-3-8-19-23-security-update-esa-2026-192/390865"},{"type":"WEB","url":"https://discuss.elastic.co/t/elasticsearch-9-4-8-9-5-5-security-update-esa-2026-190/390863"},{"type":"WEB","url":"https://msrc.microsoft.com/update-guide/"}]},{"provider":"cvelistv5","source_id":"CVE-2026-103009","relation":"self","url":"https://www.cve.org/CVERecord?id=CVE-2026-103009","license":"CC-BY-4.0","published_at":"2026-10-06T19:31:53.261Z","modified_at":"2026-10-06T19:52:13.37Z","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.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N","source":"CVE-2026-103009"}],"affected":[{"ecosystem":"CVE","package":"Elastic/Elasticsearch","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"8.13.0"},{"last_affected":"8.19.22"}]},{"type":"ECOSYSTEM","events":[{"introduced":"9.0.0"},{"last_affected":"9.4.7"}]},{"type":"ECOSYSTEM","events":[{"introduced":"9.5.0"},{"last_affected":"9.5.4"}]}],"provider":"cvelistv5","source":"CVE-2026-103009","relation":"self"}],"product_status":[],"references":[{"type":"WEB","url":"https://discuss.elastic.co/t/elasticsearch-8-19-23-9-4-8-9-5-5-security-update-esa-2026-199/390874"}]},{"provider":"osv","source_id":"BIT-elasticsearch-2026-103009","relation":"self","url":"https://osv.dev/vulnerability/BIT-elasticsearch-2026-103009","license":"Apache-2.0","published_at":"2026-10-13T06:47:26.127Z","modified_at":"2026-10-14T11:00:06.203229Z","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.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N","source":"BIT-elasticsearch-2026-103009"}],"affected":[{"ecosystem":"Bitnami","package":"elasticsearch","purl":"pkg:bitnami/elasticsearch","ranges":[{"type":"SEMVER","events":[{"introduced":"8.13.0"},{"fixed":"8.19.23"},{"introduced":"9.0.0"},{"fixed":"9.4.8"},{"introduced":"9.5.0"},{"fixed":"9.5.5"}]}],"fixed":["8.19.23","9.4.8","9.5.5"],"provider":"osv","source":"BIT-elasticsearch-2026-103009","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://discuss.elastic.co/t/elasticsearch-8-19-23-9-4-8-9-5-5-security-update-esa-2026-199/390874"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-103009"}]},{"provider":"redhat-vex","source_id":"CVE-2026-103009","relation":"self","url":"https://access.redhat.com/security/cve/CVE-2026-103009","license":"CC-BY-4.0","published_at":"2026-10-06T19:31:53.261Z","modified_at":"2026-10-31T07:20:40Z","summary":"elasticsearch: Elasticsearch: Information disclosure via crafted cross-cluster search requests","details":"A flaw was found in Elasticsearch. When processing cross-cluster search requests under the Remote Cluster Security (RCS) model, the service validates permissions using one target identifier while retrieving data using a separate identifier. An authenticated attacker possessing a valid cross-cluster API key can exploit this inconsistency by sending a crafted request with mismatched identifiers to bypass access controls. This flaw allows unauthorized information disclosure, exposing document contents, field mappings, and metadata, and may allow limited modification of retention lease states.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N","source":"CVE-2026-103009"},{"type":"Red Hat","score":"Important","source":"CVE-2026-103009"}],"affected":[],"product_status":[{"vendor":"Red Hat","product":"Red Hat OpenShift AI (RHOAI)","cpe":"cpe:/a:redhat:openshift_ai","status":"affected","packages":["rhoai/odh-feature-server-rhel9"],"package_count":1,"fixed":[],"advisories":[],"note":"Fix deferred","provider":"redhat-vex","source":"CVE-2026-103009"},{"vendor":"Red Hat","product":"Red Hat Quay 3","cpe":"cpe:/a:redhat:quay:3","status":"not_affected","packages":["quay/quay-rhel8","quay/quay-rhel9"],"package_count":2,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2026-103009"}],"references":[{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-103009.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2026-103009"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2547106"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2026-103009"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-103009"},{"type":"WEB","url":"https://discuss.elastic.co/t/elasticsearch-8-19-23-9-4-8-9-5-5-security-update-esa-2026-199/390874"}]}],"references":[{"type":"WEB","url":"https://discuss.elastic.co/t/elasticsearch-8-19-23-9-4-8-9-5-5-security-update-esa-2026-199/390874"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-103009"},{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-103009.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2026-103009"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2547106"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2026-103009"}],"sources":[{"provider":"csaf-bsi","source_id":"WID-SEC-W-2026-3784","url":"https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-3784","license":"TLP:CLEAR, mirroring permitted","modified_at":"2026-10-13T22:00:00Z","relation":"upstream"},{"provider":"cvelistv5","source_id":"CVE-2026-103009","url":"https://www.cve.org/CVERecord?id=CVE-2026-103009","license":"CC-BY-4.0","modified_at":"2026-10-06T19:52:13.37Z","relation":"self"},{"provider":"osv","source_id":"BIT-elasticsearch-2026-103009","url":"https://osv.dev/vulnerability/BIT-elasticsearch-2026-103009","license":"Apache-2.0","modified_at":"2026-10-14T11:00:06.203229Z","relation":"self"},{"provider":"redhat-vex","source_id":"CVE-2026-103009","url":"https://access.redhat.com/security/cve/CVE-2026-103009","license":"CC-BY-4.0","modified_at":"2026-10-31T07:20:40Z","relation":"self"}]}
