BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-29768High confidence

Vim vulnerable to potential data loss with zip.vim and special crafted zip files

vim · vim

Official source article: GitHub GHSA-693P-M996-3RMF ↗. Check the applicable product and release in the original source.

4.4MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 35 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.39% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs vim vim and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 35 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

6 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · mainvimVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.9.1.1202-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · mainvimVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.9.1.1202-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcevimVendor fix publishedDebian records a fixed source-package version for this release.2:9.1.1230-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcevimAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcevimVendor fix publishedDebian records a fixed source-package version for this release.2:9.1.1230-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcevimVendor fix publishedDebian records a fixed source-package version for this release.2:9.1.1230-1Debian Security Tracker ↗Source updated 6 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2025-29768 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityvim: Vim vulnerable to potential data loss with zip.vim and special crafted zip files
34 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • vim-X11 as a component of Red Hat Enterprise Linux 10
  • vim-common as a component of Red Hat Enterprise Linux 10
  • vim-data as a component of Red Hat Enterprise Linux 10
  • vim-enhanced as a component of Red Hat Enterprise Linux 10
  • vim-filesystem as a component of Red Hat Enterprise Linux 10
  • vim-minimal as a component of Red Hat Enterprise Linux 10
  • vim.src as a component of Red Hat Enterprise Linux 10
  • xxd as a component of Red Hat Enterprise Linux 10
  • vim-X11 as a component of Red Hat Enterprise Linux 6
  • vim-common as a component of Red Hat Enterprise Linux 6
  • vim-enhanced as a component of Red Hat Enterprise Linux 6
  • vim-filesystem as a component of Red Hat Enterprise Linux 6
Summary
A flaw was found in Vim's zip.vim plugin. This vulnerability allows potential data loss via specially crafted zip files when a user views the archive in Vim and presses 'x' on an unusual filename.
Remediation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-6366

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 35 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

Vim, a text editor, is vulnerable to potential data loss with zip.vim and special crafted zip files in versions prior to 9.1.1198. The impact is medium because a user must be made to view such an archive with Vim and then press 'x' on such a strange filename. The issue has been fixed as of Vim patch v9.1.1198.

What

Vim, a text editor, is vulnerable to potential data loss with zip.vim and special crafted zip files in versions prior to 9.1.1198. The impact is medium because a user must be made to view such an archive with Vim and then press 'x' on such a strange filename. The issue has been fixed as of Vim patch v9.1.1198.

Why

The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.

How

An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Vim, a text editor, is vulnerable to potential data loss with zip.vim and special crafted zip files in versions prior to 9.1.1198. The impact is medium because a user must be made to view such an archive with Vim and then press 'x' on such a strange filename. The issue has been fixed as of Vim patch v9.1.1198.

Why

The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.

How

An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-88 ↗

CWE-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection'). The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
UnauthenticatedCWE-88
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-0551vim: Schwachstelle ermöglicht Manipulation von Dateien

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in vim ausnutzen, um Dateien zu manipulieren.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250320Security Bulletin 20 Mar 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 20 Mar 2025, published on 20 March 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0969Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2025-27220 Référence CVE CVE-2025-27221 https://www.cve.org/CVERecord?id=CVE-2025-27221 Référence CVE CVE-2025-27363 https://www.cve.org/CVERecord?id=CVE-2025-27363 Référence CVE CVE-2025-27516 https://www.cve.org/CVERecord?id=CVE-2025-27516 Référence CVE CVE-2025-27587 https://www.cve.org/CVERecord?id=CVE-2025-27587 Référence CVE CVE-2025-27789 https://www.cve.org/CVERecord?id=CVE-2025-27789 Référence CVE CVE-2025-27817 https://www.cve.org/CVERecord?id=CVE-2025-27817 Référence CVE CVE-2025-27818 https://www.cve.org/CVERecord?id=CVE-2025-27818 Référence CVE CVE-2025-2953 https://www.cve.org/CVERecord?id=CVE-2025-2953 Référence CVE CVE-2025-29768 https://www.cve.org/CVERecord?id=CVE-2025-29768 Référence CVE CVE-2025-29786 https://www.cve.org/CVERecord?id=CVE-2025-29786 Référence CVE CVE-2025-2998 https://www.cve.org/CVERecord?id=CVE-2025-2998 Référence CVE CVE-2025-2999 https://www.cve.org/CVERecord?id=CVE-2025-2999 Référence CVE CVE-2025-3000 https://www.cve.org/CVERecord?id=CVE-2025-3000 Référence CVE CVE-2025-3001 https://www.cve.org/CVERecord?id=CVE-2025-3001 Référence CVE CVE-2025-30258 https://www.cve.org/CVERecord?id=CVE-2025-30258 Référence CVE CVE-2025-30681 https://www.cve.org/CVERecord?id=CVE-2025-30681 Référence CVE CVE-2025-30682 https://www.cve.org/CVERecord?id=CVE-2025

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0693Multiples vulnérabilités dans VMware Tanzu

cord?id=CVE-2025-1377 Référence CVE CVE-2025-1795 https://www.cve.org/CVERecord?id=CVE-2025-1795 Référence CVE CVE-2025-22134 https://www.cve.org/CVERecord?id=CVE-2025-22134 Référence CVE CVE-2025-22874 https://www.cve.org/CVERecord?id=CVE-2025-22874 Référence CVE CVE-2025-24014 https://www.cve.org/CVERecord?id=CVE-2025-24014 Référence CVE CVE-2025-24528 https://www.cve.org/CVERecord?id=CVE-2025-24528 Référence CVE CVE-2025-24928 https://www.cve.org/CVERecord?id=CVE-2025-24928 Référence CVE CVE-2025-25724 https://www.cve.org/CVERecord?id=CVE-2025-25724 Référence CVE CVE-2025-26603 https://www.cve.org/CVERecord?id=CVE-2025-26603 Référence CVE CVE-2025-29768 https://www.cve.org/CVERecord?id=CVE-2025-29768 Référence CVE CVE-2025-3198 https://www.cve.org/CVERecord?id=CVE-2025-3198 Référence CVE CVE-2025-3576 https://www.cve.org/CVERecord?id=CVE-2025-3576 Référence CVE CVE-2025-4138 https://www.cve.org/CVERecord?id=CVE-2025-4138 Référence CVE CVE-2025-4330 https://www.cve.org/CVERecord?id=CVE-2025-4330 Référence CVE CVE-2025-4373 https://www.cve.org/CVERecord?id=CVE-2025-4373 Référence CVE CVE-2025-4435 https://www.cve.org/CVERecord?id=CVE-2025-4435 Référence CVE CVE-2025-4516 https://www.cve.org/CVERecord?id=CVE-2025-4516 Référence CVE CVE-2025-4517 https://www.cve.org/CVERecord?id=CVE-2025-4517 R

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0585Multiples vulnérabilités dans VMware Tanzu

cord?id=CVE-2024-7531 Référence CVE CVE-2025-1215 https://www.cve.org/CVERecord?id=CVE-2025-1215 Référence CVE CVE-2025-22134 https://www.cve.org/CVERecord?id=CVE-2025-22134 Référence CVE CVE-2025-22233 https://www.cve.org/CVERecord?id=CVE-2025-22233 Référence CVE CVE-2025-22871 https://www.cve.org/CVERecord?id=CVE-2025-22871 Référence CVE CVE-2025-24014 https://www.cve.org/CVERecord?id=CVE-2025-24014 Référence CVE CVE-2025-25724 https://www.cve.org/CVERecord?id=CVE-2025-25724 Référence CVE CVE-2025-26603 https://www.cve.org/CVERecord?id=CVE-2025-26603 Référence CVE CVE-2025-27151 https://www.cve.org/CVERecord?id=CVE-2025-27151 Référence CVE CVE-2025-29768 https://www.cve.org/CVERecord?id=CVE-2025-29768 Référence CVE CVE-2025-31344 https://www.cve.org/CVERecord?id=CVE-2025-31344 Référence CVE CVE-2025-31650 https://www.cve.org/CVERecord?id=CVE-2025-31650 Référence CVE CVE-2025-31651 https://www.cve.org/CVERecord?id=CVE-2025-31651 Référence CVE CVE-2025-3576 https://www.cve.org/CVERecord?id=CVE-2025-3576 Référence CVE CVE-2025-4138 https://www.cve.org/CVERecord?id=CVE-2025-4138 Référence CVE CVE-2025-4330 https://www.cve.org/CVERecord?id=CVE-2025-4330 Référence CVE CVE-2025-4435 https://www.cve.org/CVERecord?id=CVE-2025-4435 Référence CVE CVE-2025-4517 https://www.cve.org/CVERecord?id=CVE-2025-

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-011716Vim の Vim 等複数ベンダの製品における引数の挿入または変更に関する脆弱性

Vim の Vim 等複数ベンダの製品には、引数の挿入または変更に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
04

Evidence and provenance

Published 13 Mar 2025 · Last source change 2 May 2025, 23:03 UTC · CWE-88 · Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-6366
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    vim-X11 as a component of Red Hat Enterprise Linux 10; vim-common as a component of Red Hat Enterprise Linux 10; vim-data as a component of Red Hat Enterprise Linux 10; vim-enhanced as a component of Red Hat Enterprise Linux 10; vim-filesystem as a component of Red Hat Enterprise Linux 10; vim-minimal as a component of Red Hat Enterprise Linux 10; vim.src as a component of Red Hat Enterprise Linux 10; xxd as a component of Red Hat Enterprise Linux 10; vim-X11 as a component of Red Hat Enterprise Linux 6; vim-common as a component of Red Hat Enterprise Linux 6; vim-enhanced as a component of Red Hat Enterprise Linux 6; vim-filesystem as a component of Red Hat Enterprise Linux 6; vim-minimal as a component of Red Hat Enterprise Linux 6; vim.src as a component of Red Hat Enterprise Linux 6; vim-X11 as a component of Red Hat Enterprise Linux 7; vim-common as a component of Red Hat Enterprise Linux 7; vim-enhanced as a component of Red Hat Enterprise Linux 7; vim-filesystem as a component of Red Hat Enterprise Linux 7; vim-minimal as a component of Red Hat Enterprise Linux 7; vim.src as a component of Red Hat Enterprise Linux 7; vim-X11 as a component of Red Hat Enterprise Linux 8; vim-common as a component of Red Hat Enterprise Linux 8; vim-enhanced as a component of Red Hat Enterprise Linux 8; vim-filesystem as a component of Red Hat Enterprise Linux 8; vim-minimal as a component of Red Hat Enterprise Linux 8; vim.src as a component of Red Hat Enterprise Linux 8; vim-X11 as a component of Red Hat Enterprise Linux 9; vim-common as a component of Red Hat Enterprise Linux 9; vim-enhanced as a component of Red Hat Enterprise Linux 9; vim-filesystem as a component of Red Hat Enterprise Linux 9; and 3 more
    After
    vim-X11 as a component of Red Hat Enterprise Linux 10; vim-common as a component of Red Hat Enterprise Linux 10; vim-data as a component of Red Hat Enterprise Linux 10; vim-enhanced as a component of Red Hat Enterprise Linux 10; vim-filesystem as a component of Red Hat Enterprise Linux 10; vim-minimal as a component of Red Hat Enterprise Linux 10; vim.src as a component of Red Hat Enterprise Linux 10; xxd as a component of Red Hat Enterprise Linux 10; vim-X11 as a component of Red Hat Enterprise Linux 6; vim-common as a component of Red Hat Enterprise Linux 6; vim-enhanced as a component of Red Hat Enterprise Linux 6; vim-filesystem as a component of Red Hat Enterprise Linux 6; vim-minimal as a component of Red Hat Enterprise Linux 6; vim.src as a component of Red Hat Enterprise Linux 6; vim-X11 as a component of Red Hat Enterprise Linux 7; vim-common as a component of Red Hat Enterprise Linux 7; vim-enhanced as a component of Red Hat Enterprise Linux 7; vim-filesystem as a component of Red Hat Enterprise Linux 7; vim-minimal as a component of Red Hat Enterprise Linux 7; vim.src as a component of Red Hat Enterprise Linux 7; vim-X11 as a component of Red Hat Enterprise Linux 8; vim-common as a component of Red Hat Enterprise Linux 8; vim-enhanced as a component of Red Hat Enterprise Linux 8; vim-filesystem as a component of Red Hat Enterprise Linux 8; vim-minimal as a component of Red Hat Enterprise Linux 8; vim.src as a component of Red Hat Enterprise Linux 8; vim-X11 as a component of Red Hat Enterprise Linux 9; vim-common as a component of Red Hat Enterprise Linux 9; vim-enhanced as a component of Red Hat Enterprise Linux 9; vim-filesystem as a component of Red Hat Enterprise Linux 9; and 4 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2025-6366↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference · GitHub GHSA-693P-M996-3RMF↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-29768 · cve.blacktree.nl