CVE Watchtower

CVE-2026-103009Elastic Elasticsearch Authorization Bypass Through User-Controlled Key

NVDCVSS scored by security@elastic.co

Vulnerability Summary

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 Level
HIGH(7.1)
Published Date
Oct 6, 2026
Last Modified
Oct 9, 2026
Exploitation Status
No confirmed exploitation yet
EPSS Score (30-Day)
0.24%Probability
Root Weakness (CWE)
The system does not prevent one user from accessing another user data or record by modifying the key value identifying the data.
CVSS v3.1 Base Metrics — Score 7.1 (HIGH)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityLow
AvailabilityNone

Affected & Patched Versions

Affected Versions
  • Elastic Elasticsearch >= 8.13.0 and < 8.19.23
  • Elastic Elasticsearch >= 9.0.0 and < 9.4.8
  • Elastic Elasticsearch >= 9.5.0 and < 9.5.5
Patched Versions
  • Elastic Elasticsearch 8.19.23
  • Elastic Elasticsearch 9.4.8
  • Elastic Elasticsearch 9.5.5

What to do

Plan remediation soon. No exploitation is confirmed yet, but the severity is high.

  1. Check whether you run Elastic Elasticsearch and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Oct 6, 2026Published
  • Oct 9, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new Elastic Elasticsearch CVEsYou are reading CVE-2026-103009. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

Data last checked: Nov 17, 2026 12:17 UTC