# CVE-2026-2817: Spring Data Geode Insecure Temporary Directory Usage

> Local attackers can read other users' cache data due to insecure temporary directory usage during snapshot imports in Spring Data Geode.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2026
- **Updated:** 20 Feb 2026
- **Also known as:** GHSA-qpc7-wrgr-p3hh

## What is CVE-2026-2817?

CVE-2026-2817 is a medium-severity vulnerability in VMware Spring Data Gemfire, published on 19 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-538 (Insertion of Sensitive Information into Externally-Accessible File or Directory), CWE-379 (Creation of Temporary File in Directory with Insecure Permissions), CWE-378 (Creation of Temporary File With Insecure Permissions)

## Which versions are affected by CVE-2026-2817?


## How do I fix CVE-2026-2817?

No fix has been published for CVE-2026-2817 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-2817 being exploited?

There is no known exploitation of CVE-2026-2817 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2817 and fix it if it is affected.

What it is: CVE-2026-2817 is a medium-severity vulnerability in VMware Spring Data Gemfire, published on 19 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2817 in the wild and no public exploit code.

Affected product: VMware Spring Data Gemfire. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2817/ (Markdown: https://insights.sbomify.com/CVE-2026-2817/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2817
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2817
- OSV: https://osv.dev/vulnerability/CVE-2026-2817

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2817/
Summaries are generated and may contain mistakes; the official description above is the record.