CVE-2026-103009
CVE-2026-103009 is a high-severity vulnerability in Elastic Elasticsearch with a CVSS 3.x base score of 7.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-639.
Key facts
- Severity: High (CVSS 3.x base score 7.1)
- EPSS exploit prediction: 0% (16th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-639
- Affected product: Elastic Elasticsearch
- Published:
- Last modified:
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.
Frequently asked questions
- What is 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 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.
- How severe is CVE-2026-103009?
- CVE-2026-103009 has a CVSS 3.x base score of 7.1, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity low, and availability none.
- Is CVE-2026-103009 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (16th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2026-103009?
- CVE-2026-103009 affects Elastic Elasticsearch. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2026-103009?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2026-103009 published?
- CVE-2026-103009 was published on 2026-10-06 and last updated on 2026-10-09.
References
Affected products (1)
- cpe:2.3:a:elastic:elasticsearch:*:*:*:*:*:*:*:*
More vulnerabilities in Elastic Elasticsearch
- CVE-2015-5377 — Critical (CVSS 9.8): Elasticsearch before 1.6.1 allows remote attackers to execute arbitrary code via unspecified vectors involving the…
- CVE-2015-1427 — Critical (CVSS 9.8): The Groovy scripting engine in Elasticsearch before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to bypass the…
- CVE-2026-72649 — High (CVSS 8.8): Deserialization of Untrusted Data (CWE-502) in the Elasticsearch machine learning component can lead to remote code…
- CVE-2026-72642 — High (CVSS 8.8): The native inference process that Elasticsearch uses to evaluate uploaded machine learning models accepts a model…
- CVE-2020-7014 — High (CVSS 8.8): The fix for CVE-2020-7009 was found to be incomplete. Elasticsearch versions from 6.7.0 to 6.8.7 and 7.0.0 to 7.6.1…
- CVE-2020-7009 — High (CVSS 8.8): Elasticsearch versions from 6.7.0 before 6.8.8 and 7.0.0 before 7.6.2 contain a privilege escalation flaw if an…
All CVEs affecting Elastic Elasticsearch →
Other CWE-639 (Authorization Bypass Through User-Controlled Key (IDOR)) vulnerabilities
- CVE-2026-109469 — Critical (CVSS 10.0): Authorization bypass through user-controlled key in Entra Device Registration allows an unauthorized attacker to…
- CVE-2024-34323 — Critical (CVSS 10.0): ProPhoenix Law RMS v2022.2403.3.101 was discovered to contain an Insecure Direct Object Reference (IDOR) via the…
- CVE-2026-69865 — Critical (CVSS 10.0): Authorization bypass through user-controlled key in Microsoft Container Registry allows an unauthorized attacker to…
- CVE-2026-83711 — Critical (CVSS 10.0): Authorization bypass through user-controlled key in Microsoft Azure Active Directory B2C allows an unauthorized…
- CVE-2026-77998 — Critical (CVSS 10.0): Joomla Extension - miniorange.com - Unauthenticated Authentication Bypass via SAMLResponse Parameter in miniOrange SAML…
- CVE-2026-77995 — Critical (CVSS 10.0): Joomla Extension - miniorange.com - Arbitrary account takeover in miniOrange OAuth Client < 3.2.0, OAuth Single Sign-On…
Browse all CWE-639 (Authorization Bypass Through User-Controlled Key (IDOR)) vulnerabilities →