CVE-2026-103009 Affecting elasticsearch-9.5-oci-entrypoint package, versions <9.5.5-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-MINIMOSLATEST-ELASTICSEARCH95OCIENTRYPOINT-20820166
- published11 Oct 2026
- disclosed6 Oct 2026
Introduced: 6 Oct 2026
NewCVE-2026-103009 (opens in a new tab)How to fix?
Upgrade Minimos:latest elasticsearch-9.5-oci-entrypoint to version 9.5.5-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream elasticsearch-9.5-oci-entrypoint package and not the elasticsearch-9.5-oci-entrypoint package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
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.