VMware Spring Data Geode/Spring Data Gemfire file information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in VMware Spring Data Geode and Spring Data Gemfire. This affects an unknown part. This manipulation causes file information disclosure. This vulnerability only affects products that are no longer supported by the maintainer. This vulnerability is registered as CVE-2026-2817. The attack needs to be launched locally. No exploit is available.
Details
A vulnerability was found in VMware Spring Data Geode and Spring Data Gemfire (version now known). It has been declared as problematic. Affected by this vulnerability is some unknown processing. The manipulation with an unknown input leads to a file information disclosure vulnerability. The CWE definition for the vulnerability is CWE-538. The product places sensitive information into files or directories that are accessible to actors who are allowed to have access to the files, but not to the sensitive information. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Use of insecure directory in Spring Data Geode snapshot import extracts archives into predictable, permissive directories under the system temp location. On shared hosts, a local user with basic privileges can access another user’s extracted snapshot contents, leading to unintended exposure of cache data.
It is possible to read the advisory at herodevs.com. This vulnerability is known as CVE-2026-2817 since 02/19/2026. The exploitation appears to be easy. Attacking locally is a requirement. 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 02/19/2026). The attack technique deployed by this issue is T1083 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.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
License
Support
Website
- Vendor: https://www.vmware.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.9VulDB Meta Temp Score: 4.9
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.4
CNA Vector (HeroDevs): 🔒
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: File information disclosureCWE: CWE-538 / CWE-200 / CWE-284
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
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
02/19/2026 Advisory disclosed02/19/2026 CVE reserved
02/19/2026 VulDB entry created
02/19/2026 VulDB entry last update
Sources
Vendor: vmware.comAdvisory: herodevs.com
Status: Not defined
CVE: CVE-2026-2817 (🔒)
GCVE (CVE): GCVE-0-2026-2817
GCVE (VulDB): GCVE-100-346975
scip Labs: https://www.scip.ch/en/?labs.20060413
Entry
Created: 02/19/2026 21:49Changes: 02/19/2026 21:49 (73)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.