Vulnerability in vim (ALPINE-CVE-2025-22134)

Summary

Vulnerability in vim (ALPINE-CVE-2025-22134). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 9.1.1003-r0 or later.

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: OSV.dev (Open Source Vulnerabilities) OSV

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 ALPINE-CVE-2025-22134 has been found in vim.
Risk of unauthorized operations or information disclosure.
What to do: upgrade vim to 9.1.1003-r0 or later.
If unsure, ask your IT team or search "vim ALPINE-CVE-2025-22134" on the vendor's site.

ALPINE-CVE-2025-22134 (vim)
Attack vector: local / unauthenticated
Patched: 9.1.1003-r0 — 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.

❓ What is the problem

A vulnerability (unclassified) exists in vim.

📍 Affected scope

Check the vendor advisory for the affected versions of vim.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 9.1.1003-r0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

1
Identify exposure identify
```
grep -r 'vim' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で vim を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade vim to 9.1.1003-r0
```
ステージング環境で 9.1.1003-r0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Alpine:v3.21 vim

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.1.1003-r0"}]}]

Alpine:v3.22 vim

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.1.1003-r0"}]}]

Alpine:v3.23 vim

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.1.1003-r0"}]}]

References

advisory security.alpinelinux.org