cve.bz

CVE-2026-103009 elastic elasticsearch

7.1 highEPSS 0.2%

High (7.1) in elastic elasticsearch. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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

CVSS 3.1

7.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-639 Authorization Bypass Through User-Controlled Key
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-103009 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-103009?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-103009?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-103009 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Elasticsearchfrom 8.13.0 through 8.19.22
Elasticsearchfrom 9.0.0 through 9.4.7
Elasticsearchfrom 9.5.0 through 9.5.4

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as having an Important severity because an authenticated user with cross-cluster search privileges can circumvent tenancy boundaries to view sensitive documents, schema mappings, and index metadata without proper permissions. The elevated severity reflects the high confidentiality impact across separated indices, though the necessity of existing API key credentials and a Remote Cluster Security (RCS) 2.0 architecture prevents it from being Critical. Within Red Hat deployments, exposure is limited to configurations actively utilizing remote cluster connections with API key authentication, while standard single-cluster installations or environments using certificate-based cluster security remain unaffected.

ProductPackageStateAdvisory
Red Hat OpenShift AI (RHOAI)rhoai/odh-feature-server-rhel9Fix deferred
Red Hat Quay 3quay/quay-rhel8Not affected
Red Hat Quay 3quay/quay-rhel9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-103009.

References

Check your stackJSON