CVE-2026-2818
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA zip-slip path traversal vulnerability exists in Spring Data Geode's import snapshot functionality. The vulnerability allows an attacker to craft a malicious ZIP archive containing files with path traversal sequences (e.g., ../../../evil.jar) that, when extracted on Windows systems, write files outside the intended extraction directory. This occurs due to insufficient validation of file paths within the archive before extraction.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Spring Data Geode is installedSearch for spring-data-geode JAR files in your application classpath, dependencies, or installed libraries. Check build files (pom.xml, build.gradle) for spring-data-geode or spring-geode dependencies.Affected if Spring Data Geode is present in the environment
-
Identify the installed versionLocate the spring-data-geode or spring-geode JAR file and check its version in the filename or manifest, or look up the version in your dependency management system (Maven/Gradle).Affected if The version is unknown or falls within a vulnerable range that includes this path traversal issue
-
Verify the operating system is WindowsCheck the operating system where Spring Data Geode is running by running 'systeminfo' on Windows or checking OS detection in your deployment configuration.Affected if The environment is running on Windows; this vulnerability is specific to Windows systems
-
Determine if import snapshot functionality is in useSearch code and configuration for usage of import snapshot feature - look for classes handling snapshot import, deserialization of zip-based data, or GemFire/Geode import operations. Check for references to SnapshotService, SnapshotOptions, or similar import APIs.Affected if The import snapshot feature is actively used or configured in the application
-
Check if zip archives are processedReview application logs, code, or runtime behavior for zip extraction operations, particularly during data import or snapshot restore operations.Affected if The application processes zip archives for data import, especially from untrusted or external sources
You are affected if Spring Data Geode is installed, running on Windows, the import snapshot feature is enabled, and your application extracts files from zip archives using the vulnerable functionality.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the official patch or upgrade to a patched version of Spring Data Geode once available. As a temporary workaround, validate all entries in ZIP files before extraction and ensure extracted paths resolve within the intended directory.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2818 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2818 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data