Elastic Elasticsearch up to 8.19.23/9.4.8/9.5.5 Cache cache containing sensitive information
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.37 |
Summary
A vulnerability has been found in Elastic Elasticsearch up to 8.19.23/9.4.8/9.5.5 and classified as critical. Affected by this issue is some unknown functionality of the component Cache. The manipulation leads to use of cache containing sensitive information. This vulnerability is referenced as CVE-2026-115710. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in Elastic Elasticsearch up to 8.19.23/9.4.8/9.5.5 and classified as critical. This issue affects an unknown part of the component Cache. The manipulation with an unknown input leads to a use of cache containing sensitive information vulnerability. Using CWE to declare the problem leads to CWE-524. The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Use of Cache Containing Sensitive Information (CWE-524) in Elasticsearch can lead to information disclosure and incorrect search results via specially crafted search requests. For some query types, Elasticsearch can share cached query results between users who have field-level security restrictions and users who do not. A user restricted by field-level security can learn which documents match a value in a field that they cannot read. A restricted user can also cause users with full access to receive incomplete search results. Disclosure is only possible when a user with full access ran the same query on the same shard recently.
It is possible to read the advisory at discuss.elastic.co. The identification of this vulnerability is CVE-2026-115710 since 10/23/2026. The exploitation is known to be easy. The attack may be initiated remotely. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/03/2026). The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
- 8.19.0
- 8.19.1
- 8.19.2
- 8.19.3
- 8.19.4
- 8.19.5
- 8.19.6
- 8.19.7
- 8.19.8
- 8.19.9
- 8.19.10
- 8.19.11
- 8.19.12
- 8.19.13
- 8.19.14
- 8.19.15
- 8.19.16
- 8.19.17
- 8.19.18
- 8.19.19
- 8.19.20
- 8.19.21
- 8.19.22
- 8.19.23
- 9.4.0
- 9.4.1
- 9.4.2
- 9.4.3
- 9.4.4
- 9.4.5
- 9.4.6
- 9.4.7
- 9.4.8
- 9.5.0
- 9.5.1
- 9.5.2
- 9.5.3
- 9.5.4
- 9.5.5
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.9VulDB Meta Temp Score: 4.9
VulDB Base Score: 5.5
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.2
CNA Vector (elastic): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Use of cache containing sensitive informationCWE: CWE-524
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/23/2026 CVE reserved11/03/2026 Advisory disclosed
11/03/2026 VulDB entry created
11/03/2026 VulDB entry last update
Sources
Advisory: discuss.elastic.coStatus: Confirmed
CNA: elastic
CVE: CVE-2026-115710 (🔒)
GCVE (CVE): GCVE-0-2026-115710
GCVE (VulDB): GCVE-100-430475
Entry
Created: 11/03/2026 18:12Changes: 11/03/2026 18:12 (61)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.