Vulnerability in vim
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 UBUNTU-CVE-2026-41411 has been found in vim.
Attackers can target a specific entry point like command over the network to misuse the product.
Data can be tampered with by attackers.
What to do: upgrade vim to 2:7.4.052-1ubuntu3.1+esm27 or later.
If unsure, ask your IT team or search "vim UBUNTU-CVE-2026-41411" on the vendor's site.
UBUNTU-CVE-2026-41411 (vim)
Attack vector: local / unauthenticated
Attack surface: command
Patched: 2:7.4.052-1ubuntu3.1+esm27 — 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.
A vulnerability (unclassified) exists in vim. Attackers reach the vulnerable code path via command without authentication.
Check the vendor advisory for the affected versions of vim. Attack surface: command.
Severity: ?. Data can be tampered with by attackers.
Update to 2:7.4.052-1ubuntu3.1+esm27.
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
-
1
Identify exposureidentify
grep -r 'vim' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
vimを grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade vim to 2:7.4.052-1ubuntu3.1+esm27ステージング環境で 2:7.4.052-1ubuntu3.1+esm27 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| Ubuntu:Pro:14.04:LTS | vim |
< 2:7.4.052-1ubuntu3.1+esm27 |
2:7.4.052-1ubuntu3.1+esm27 |
| Ubuntu:Pro:16.04:LTS | vim |
< 2:7.4.1689-3ubuntu1.5+esm33 |
2:7.4.1689-3ubuntu1.5+esm33 |
| Ubuntu:Pro:18.04:LTS | vim |
< 2:8.0.1453-1ubuntu1.13+esm18 |
2:8.0.1453-1ubuntu1.13+esm18 |
| Ubuntu:Pro:20.04:LTS | vim |
< 2:8.1.2269-1ubuntu5.32+esm6 |
2:8.1.2269-1ubuntu5.32+esm6 |
| Ubuntu:22.04:LTS | vim |
< 2:8.2.3995-1ubuntu2.29 |
2:8.2.3995-1ubuntu2.29 |
| Ubuntu:24.04:LTS | vim |
< 2:9.1.0016-1ubuntu7.13 |
2:9.1.0016-1ubuntu7.13 |
| Ubuntu:25.10 | vim |
< 2:9.1.0967-1ubuntu6.4 |
2:9.1.0967-1ubuntu6.4 |
| Ubuntu:26.04 | vim |
< 2:9.1.2141-1ubuntu4.1 |
2:9.1.2141-1ubuntu4.1 |
| Ubuntu:26.04:LTS | vim |
< 2:9.1.2141-1ubuntu4.1 |
2:9.1.2141-1ubuntu4.1 |
Original description The description as published by the source.
Vim is an open source, command line text editor. Prior to 9.2.0357, A command injection vulnerability exists in Vim's tag file processing. When resolving a tag, the filename field from the tags file is passed through wildcard expansion to resolve environment variables and wildcards. If the filename field contains backtick syntax (e.g., command), Vim executes the embedded command via the system shell with the full privileges of the running user.
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- advisory ubuntu.com
- advisory ubuntu.com
- report ubuntu.com
- report cve.org
- report github.com
- report github.com