Vulnerability in Neovim (CVE-2025-22134)
Summary
Vulnerability in Neovim (CVE-2025-22134). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
When switching to other buffers using the :all command and visual mode still being active, this may cause a heap-buffer overflow, because Vim does not properly end visual mode and therefore may try to access beyond the end of a line in a buffer. In Patch 9.1.1003 Vim will correctly reset the visual mode before opening other windows and buffers and therefore fix this bug. In addition it does verify that it won't try to access a position if the position is greater than the corresponding buffer line. Impact is medium since the user must have switched on visual mode when executing the :all ex command. The Vim project would like to thank github user gandalf4a for reporting this issue. The issue has been fixed as of Vim patch v9.1.1003
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-2025-22134 has been found in Neovim.
Risk of unauthorized operations or information disclosure. CVSS score: 4.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Neovim CVE-2025-22134" on the vendor's site.
CVE-2025-22134 (Neovim) — CWE-122 / CVSS v3 4.2
Attack vector: local
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.
A vulnerability (CWE-122) exists in Neovim.
Check the vendor advisory for the affected versions of Neovim.
Severity: Medium (CVSS 4.2/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
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 'Neovim' . 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 'Neovim' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Neovimを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-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-2025-22134 vim Fixed in: 9.1.1003-r0
- Debian DEBIAN-CVE-2025-22134 vim
- Ubuntu UBUNTU-CVE-2025-22134 vim
References
- advisory openwall.com
- advisory security.netapp.com
- patch security-advisories@github.com
- patch security-advisories@github.com