dbcve.org
VimApplication

CVE-2026-59858

HIGH · 7.8 CVSS v3.1 Published 2026-07-09
Fix available
A fix is available. Upgrade to 9.2.0735 or later.
See remediation →
81/100
Remediation priority · High
No privileges Patch available 6 weeks old

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 · unedited
Vim is an open source, command line text editor. Prior to 9.2.0735, the C omni-completion script in runtime/autoload/ccomplete.vim interpolates the typeref: or typename: extension field of a tags entry, without escaping, into a :vimgrep pattern that is run through :execute. Because :vimgrep honors the bar as a command separator, a crafted tag field can close the search pattern and append an arbitrary Ex command; opening a hostile .c file whose project tags file contains such an entry and invoking C omni-completion runs that command as the editing user. This issue is fixed in version 9.2.0735.

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 confidence

The C omni-completion feature in Vim (runtime/autoload/ccomplete.vim) unsafely interpolates the typeref: or typename: extension fields from a tags file into a :vimgrep pattern executed via :execute. Since :vimgrep treats | as a command separator, a maliciously crafted tags entry can inject arbitrary Ex commands that execute when a user invokes C omni-completion on a hostile .c file.

MitigationUpgrade Vim to version 9.2.0735 or later. Avoid opening untrusted .c files with custom tags files from unknown sources until patched.

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
VimApplication
Affected:< 9.2.0735

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Vim version
    Run `vim --version` or `vim -version` and look for the version number in the first line (e.g., Vim version 9.2.xxx)
    Affected if The version shown is less than 9.2.0735 (for example, 9.2.0500, 9.1.x, or any version below 9.2.0735)
  2. Verify vulnerable file exists
    Locate the file `runtime/autoload/ccomplete.vim` in your Vim installation directory (common paths: /usr/share/vim/vimXX/ or C:\Program Files\Vim\vimXX\)
    Affected if The file exists at runtime/autoload/ccomplete.vim in your Vim installation path
  3. Confirm C omni-completion is available
    In Vim, run `:call cmdp#initialization()` or check that `runtime/autoload/ccomplete.vim` loads when editing a .c file (use `:scriptnames` after opening a C file)
    Affected if The ccomplete.vim script loads or is listed in scriptnames when editing a .c file
  4. Check for tags file presence
    When editing a .c file, run `:set tags?` to see if a tags file is configured, or check for a `tags` file in the current directory
    Affected if A tags file is configured or present in the working directory

You are affected if your Vim version is below 9.2.0735 AND you use C omni-completion on .c files with tags files that may contain untrusted typeref or typename fields.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 9.2.0735 or later
Fixed in 9.2.0735
Vendor patch github.com →
Interim mitigation

Upgrade Vim to version 9.2.0735 or later. Avoid opening untrusted .c files with custom tags files from unknown sources until patched.

Recommended fix High confidence

9.2.0735

  1. Check current Vim version with `vim --version`
  2. For Linux systems: update via package manager (Debian/Ubuntu: `sudo apt update && sudo apt install vim`, RHEL/CentOS: `sudo dnf update vim`, Arch: `sudo pacman -Syu vim`)
  3. For macOS: `brew upgrade vim` or download from vim.org
  4. Alternatively, build from source: clone https://github.com/vim/vim, checkout tag v9.2.0735 or later, configure and make
  5. Verify the fix by running `vim --version` and confirming the version is 9.2.0735 or higher
Caveat Minor: Some custom vimrc settings or plugins may need adjustment for the new version; review plugin compatibility if needed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vim Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-59858 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-59858 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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