CVE-2026-35177
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 · uneditedVim is an open source, command line text editor. Prior to 9.2.0280, a path traversal bypass in Vim's zip.vim plugin allows overwriting of arbitrary files when opening specially crafted zip archives, circumventing the previous fix for CVE-2025-53906. This vulnerability is fixed in 9.2.0280.
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 confidencePath traversal bypass in Vim's zip.vim plugin allows overwriting arbitrary files by opening specially crafted zip archives containing path traversal sequences (e.g., '../'), circumventing the previous fix for CVE-2025-53906.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 9.2.0280CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
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.
-
Check installed Vim versionRun 'vim --version' or 'vim -version' to display version information. Look for the version number in the output.Affected if The version shown is lower than 9.2.0280 (e.g., 9.1.x, 9.0.x, or earlier)
-
Locate the zip.vim plugin fileSearch for 'zip.vim' in Vim's runtime plugin directory. Common locations include ~/.vim/plugin/ or the system-wide vimfiles/plugin/ directory. Use 'find' or 'ls' to locate it.Affected if The file exists and was last modified before the patch date for version 9.2.0280, or if its content shows it is from an unpatched version
-
Verify zip plugin is loadedOpen Vim and run ':scriptnames' to list all loaded scripts. Search for 'zip.vim' in the output.Affected if zip.vim appears in the loaded scripts list and the Vim version is below 9.2.0280
-
Check for netrw file handlingVim often uses zip support through the netrw plugin. Run ':echo has('zip')' in Vim to check if zip support is compiled in or available.Affected if Returns 1 (true) and Vim version is below 9.2.0280
You are affected if Vim version is below 9.2.0280 and the zip.vim plugin or zip support is present and enabled on your system.
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.
dbcve · scoped9.2.0280
Upgrade Vim to version 9.2.0280 or later to apply the patch that fixes this path traversal bypass vulnerability.
9.2.0280
- Upgrade Vim to version 9.2.0280 or later to resolve the path traversal bypass in the zip.vim plugin
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35177 — 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-35177 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