Out-of-Bounds Read in Vim (CVE-2026-57452)
Summary
Vulnerability in Vim (CVE-2026-57452). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 9.2.0671 or later.
Original description
The description as published by the source.
Vim is an open source, command line text editor. Prior to 9.2.0671, when Vim opens a file encrypted with the VimCrypt04! or VimCrypt05!
method (xchacha20poly1305, requires the +sodium feature) whose body is shorter than a single libsodium secretstream header, an unsigned length calculation underflows and a subsequent decryption call reads far past the end of the input buffer, crashing Vim. This vulnerability is fixed in 9.2.0671.
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-57452 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.0671 or later.
If unsure, ask your IT team or search "Vim CVE-2026-57452" on the vendor's site.
CVE-2026-57452 (Vim) — CWE-125 / CVSS v3 5.5
Attack vector: local / unauthenticated
Patched: 9.2.0671 — 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 read (CWE-125) 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.0671.
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.0671ステージング環境で 9.2.0671 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- Alpine Linux ALPINE-CVE-2026-57452 vim Fixed in: 9.2.0854-r0
- BellSoft Alpaquita BELL-CVE-2026-57452 vim Fixed in: 9.2.0747-r0
- Debian DEBIAN-CVE-2026-57452 vim
- Ubuntu UBUNTU-CVE-2026-57452 vim Fixed in: 2:8.2.3995-1ubuntu2.33