CVE-2026-2818: Zip Slip Path Traversal in Snapshot Archive Extraction (Windows-Specific)
A zip-slip path traversal vulnerability in Spring Data Geode's import snapshot functionality allows attackers to write files outside the intended extraction directory. This vulnerability appears to be susceptible on Windows OS only.
Security readout for executives and security teams
Plain-English summary
CVE-2026-2818 is a high-severity file-write risk in Spring Data Geode snapshot archive import. A malicious archive could cause files to be written outside the intended extraction folder. The provided sources say the issue appears Windows-specific and affects listed Spring Data Geode/GemFire package versions.
Executive priority
Treat this as high priority for Windows environments using the affected packages, especially where snapshot archives cross trust boundaries. Urgency is lower where the vulnerable versions are absent, imports are unused, or systems are not Windows-based.
Technical view
The issue is a Zip Slip path traversal in snapshot archive extraction, mapped to CWE-22 and CWE-23. The CVSS 3.1 score is 8.2 with network attack vector, low complexity, no privileges, required user interaction, changed scope, low confidentiality impact, and high integrity impact.
Likely exposure
Exposure is most likely where Windows systems use org.springframework.data:spring-data-geode 2.0.0.RELEASE or org.springframework.data:spring-data-gemfire 1.7.0.RELEASE and import snapshot archives. Non-Windows exposure is not supported by the provided description.
Exploitation context
The source bundle does not identify active exploitation, and KEV status is false. Exploitation would depend on a vulnerable Windows deployment processing a malicious snapshot archive through the affected import functionality. The sources do not provide public exploit status.
Researcher notes
Evidence is specific but limited. The bundle names vulnerable versions and Windows specificity, but does not include patch details, exploit indicators, or broad product impact. Validate dependency reachability and archive trust boundaries before escalating beyond affected Windows import workflows.
Mitigation direction
Inventory applications for the listed Spring Data Geode and GemFire package versions.
Prioritize Windows deployments that import or accept snapshot archives.
Check vendor and HeroDevs guidance for supported fixed or replacement versions.
Avoid processing untrusted snapshot archives until vendor guidance is applied.
Restrict snapshot import workflows to trusted operators and controlled sources.
Validation and detection
Review SBOMs and build manifests for the affected Maven package names and versions.
Confirm whether vulnerable applications run on Windows hosts.
Identify whether snapshot import functionality is enabled or operationally used.
Check whether snapshot archives can originate from users, partners, or external systems.
Document compensating controls around archive intake and operator approval.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
ADP timelineredhat-SADP
Made public.
Feb 20, 2026, 16:03 UTC (UTC+00:00)
CVE publishedCVE Program
The CVE record was published.
Feb 20, 2026, 16:03 UTC (UTC+00:00)
ADP timelineredhat-SADP
Reported to Red Hat.
Feb 20, 2026, 17:03 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Jul 15, 2026, 01:12 UTC (UTC+00:00)
ADP provider summaries
CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPorg.springframework.data/spring-data-geode: Spring Data Geode: Path traversal vulnerability allows arbitrary file write via import snapshot functionality.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Relative Path Traversal represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.