{
  "id": "CVE-2026-103009",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-103009",
  "published_at": "2026-10-06T19:31:53.261Z",
  "title": "Authorization Bypass Through User-Controlled Key in Elasticsearch Leading to Information Disclosure",
  "vendor": "Elastic",
  "product": "Elasticsearch",
  "cvss": {
    "score": 7.1,
    "source": "cna",
    "vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "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.",
  "cwe": "CWE-639",
  "cpes": [
    "cpe:2.3:a:elastic:elasticsearch:*:*:*:*:*:*:*:*"
  ],
  "cvss_by_source": {
    "cna": 7.1
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Elastic",
        "product": "Elasticsearch",
        "ranges": [
          "\u003e= 8.13.0, \u003c= 8.19.22",
          "\u003e= 9.0.0, \u003c= 9.4.7",
          "\u003e= 9.5.0, \u003c= 9.5.4"
        ],
        "fixed_in": null
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
