CVE-2026-2817VulnerabilityPublished 19 Feb 2026Updated 20 Feb 2026

CVE-2026-2817: VMware Spring Data Geode · Insertion of Sensitive Information into Externally-Accessible File or Directory

Affects VMware Spring Data GeodeSource CVE Database V5

Not known to be exploited · CVSS 4.4 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
VMwareSpring Data Geode	Affected >=2.0.0.RELEASE <=2.7.18	Fixed in–
VMwareSpring Data Gemfire	Affected >=1.7.0.RELEASE <=2.2.13.RELEASE	Fixed in–
GitHuborg.springframework.data:spring-data-geode`pkg:github/org.springframework.data:spring-data-geode`Other threats	Affected >=2.0.0.RELEASE <=2.7.18	Fixed in–
GitHuborg.springframework.data:spring-data-gemfire`pkg:github/org.springframework.data:spring-data-gemfire`Other threats	Affected >=1.7.0.RELEASE <=2.2.13.RELEASE	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

In the interim, administrators should restrict access to the system temporary directories to prevent unauthorized local users from reading snapshot extraction directories. This can be achieved by configuring stricter filesystem permissions on the temp folder or by running Spring Data Geode processes under dedicated, isolated user accounts with minimal privileges. Additionally, consider configuring the snapshot import process to use custom, non-predictable, and access-controlled directories for extraction if supported. Monitoring and auditing access to temporary directories can help detect unauthorized access attempts. For environments where multiple users share the same host, consider isolating workloads using containerization or virtualization to prevent cross-user data exposure. Finally, review and harden local user privilege assignments to minimize the number of users who can access the system temp directory.

Description

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.

Impact

The primary impact of CVE-2026-2817 is the unintended exposure of sensitive cache data stored in Spring Data Geode snapshots. In multi-tenant or shared hosting environments, local users with basic privileges can access snapshot contents extracted by other users, potentially leading to data leakage. This can compromise confidentiality and integrity of cached information, which may include sensitive business data or personally identifiable information depending on the application. While the vulnerability does not affect system availability, the exposure of sensitive data can have significant compliance and privacy ramifications. Organizations relying on Spring Data Geode in shared environments or on systems with multiple users are at increased risk. Attackers with local access can leverage this vulnerability to gain insights into cached data, potentially facilitating further attacks or data exfiltration. The scope is limited to local privilege scenarios, reducing risk in single-user or isolated deployments, but the impact remains notable in cloud, containerized, or shared server contexts.

CWE-538Insertion of Sensitive Information into Externally-Accessible File or Directory (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
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.
Architecture and Design · Operation · System Configuration
Do not expose file and directory information to the user.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
WSDL Scanning (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-378Creation of Temporary File With Insecure Permissions (opens in a new tab)
Base weaknessLikelihood of exploit: High
Opening temporary files without appropriate measures or controls can leave the file, its contents and any function that it impacts vulnerable to attack.
Requirements
Many contemporary languages have functions which properly handle this condition. Older C temp file functions are especially susceptible.
Implementation
Ensure that you use proper file permissions. This can be achieved by using a safe temp file function. Temporary files should be writable and readable only by the process that owns the file.
Implementation
Randomize temporary file names. This can also be achieved by using a safe temp-file function. This will ensure that temporary files will not be created in predictable places.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-379Creation of Temporary File in Directory with Insecure Permissions (opens in a new tab)
Base weaknessLikelihood of exploit: LowOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product creates a temporary file in a directory whose permissions allow unintended actors to determine the file's existence or otherwise access that file.
Requirements
Many contemporary languages have functions which properly handle this condition. Older C temp file functions are especially susceptible.
Implementation
Try to store sensitive tempfiles in a directory which is not world readable -- i.e., per-user directories.
Implementation
Avoid using vulnerable temp file functions.
OWASP Cheat Sheets
Authorization (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

herodevs.com/vulnerability-directory/cve-2026-2817 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 14:13 UTC

WeaknessesCWE-538, CWE-378, CWE-379

Technical details

References

Community reviews

Related threats