Out-of-Bounds Write in Vim (CVE-2026-55892)
Summary
Out-of-bounds write in Vim (CVE-2026-55892). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 9.2.0662 or later.
Original description
The description as published by the source.
Vim is an open source, command line text editor. Prior to 9.2.0662, the dump_prefixes() function in src/spell.c walks a spell-file prefix trie iteratively with a depth counter while dumping the prefixes that apply to a word. The counter is bounded only by the trie structure itself; it is never checked against the size of the fixed MAXWLEN-element stack arrays it indexes (prefix[], arridx[], curi[]). A crafted .spl file, loaded when the user dumps the word list, can drive the descent arbitrarily deep, so the function writes past the end of those arrays. This is a stack out-of-bounds write that corrupts the call frame and crashes the editor. This vulnerability is fixed in 9.2.0662.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55892 has been found in Vim.
Risk of unauthorized operations or information disclosure. CVSS score: 5.5/10.
What to do: upgrade Vim to 9.2.0662 or later.
If unsure, ask your IT team or search "Vim CVE-2026-55892" on the vendor's site.
CVE-2026-55892 (Vim) — CWE-787 / CVSS v3 5.5
Attack vector: local / unauthenticated
Patched: 9.2.0662 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Out-of-bounds write (CWE-787) exists in Vim.
Check the vendor advisory for the affected versions of Vim.
Severity: Medium (CVSS 5.5/10). Risk of unauthorized operations or information disclosure.
Update to 9.2.0662.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Vim' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Vim' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Vimを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Vim to 9.2.0662ステージング環境で 9.2.0662 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- BellSoft Alpaquita BELL-CVE-2026-55892 vim Fixed in: 9.2.0747-r0
- Ubuntu UBUNTU-CVE-2026-55892 vim Fixed in: 2:7.4.052-1ubuntu3.1+esm30