# CVE-2026-41411: Vim: Command injection via backtick expansion in tag filenames

> Attackers can execute arbitrary system commands via backtick syntax in tag filenames, requiring users to open malicious tag files.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Apr 2026
- **Updated:** 28 Apr 2026
- **Also known as:** ALPINE-CVE-2026-41411, ALSA-2026:28209, ALSA-2026:28210, ALSA-2026:28553, AZL-84047, BELL-CVE-2026-41411, CLSA-2026-1780708480, CLSA-2026-1780713496, CLSA-2026-1781010825, CLSA-2026-1781030937, CLSA-2026-1781081927, CLSA-2026-1781082148, CLSA-2026-1781082176, CLSA-2026-1781086654, CLSA-2026-1785846808, DEBIAN-CVE-2026-41411, ECHO-c375-87d8-ee8b, GHSA-cwgx-gcj7-6qh8, OESA-2026-2201, OESA-2026-2202, OESA-2026-2203, OESA-2026-2204, OESA-2026-2297, RHSA-2026:28209, RHSA-2026:28210, RHSA-2026:28553, RLSA-2026:28209, RLSA-2026:28210, RLSA-2026:28553, UBUNTU-CVE-2026-41411, USN-8342-1

## What is CVE-2026-41411?

CVE-2026-41411 is a medium-severity command injection vulnerability in Vim Vim, published on 24 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-41411?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vim-X11` | AlmaLinux:10 | All versions | 2:9.1.083-9.el10_2.4 |
| `vim-common` | AlmaLinux:10 | All versions | 2:9.1.083-9.el10_2.4 |
| `vim-data` | AlmaLinux:10 | All versions | 2:9.1.083-9.el10_2.4 |
| `vim-enhanced` | AlmaLinux:10 | All versions | 2:9.1.083-9.el10_2.4 |
| `vim-filesystem` | AlmaLinux:10 | All versions | 2:9.1.083-9.el10_2.4 |
| `vim-minimal` | AlmaLinux:10 | All versions | 2:9.1.083-9.el10_2.4 |
| `xxd` | AlmaLinux:10 | All versions | 2:9.1.083-9.el10_2.4 |
| `vim-X11` | AlmaLinux:8 | All versions | 2:8.0.1763-24.el8_10 |
| `vim-common` | AlmaLinux:8 | All versions | 2:8.0.1763-24.el8_10 |
| `vim-enhanced` | AlmaLinux:8 | All versions | 2:8.0.1763-24.el8_10 |
| `vim-filesystem` | AlmaLinux:8 | All versions | 2:8.0.1763-24.el8_10 |
| `vim-minimal` | AlmaLinux:8 | All versions | 2:8.0.1763-24.el8_10 |
| `vim-X11` | AlmaLinux:9 | All versions | 2:8.2.2637-26.el9_8.6 |
| `vim-common` | AlmaLinux:9 | All versions | 2:8.2.2637-26.el9_8.6 |
| `vim-enhanced` | AlmaLinux:9 | All versions | 2:8.2.2637-26.el9_8.6 |
| `vim-filesystem` | AlmaLinux:9 | All versions | 2:8.2.2637-26.el9_8.6 |
| `vim-minimal` | AlmaLinux:9 | All versions | 2:8.2.2637-26.el9_8.6 |
| `vim` | Red Hat:enterprise_linux:10.2 | All versions | 2:9.1.083-9.el10_2.4 |
| `vim-X11` | Red Hat:enterprise_linux:10.2 | All versions | 2:9.1.083-9.el10_2.4 |
| `vim-enhanced` | Red Hat:enterprise_linux:10.2 | All versions | 2:9.1.083-9.el10_2.4 |
| `vim-minimal` | Red Hat:enterprise_linux:10.2 | All versions | 2:9.1.083-9.el10_2.4 |
| `vim-X11` | Red Hat:enterprise_linux:8::appstream | All versions | 2:8.0.1763-24.el8_10 |
| `vim-enhanced` | Red Hat:enterprise_linux:8::appstream | All versions | 2:8.0.1763-24.el8_10 |
| `vim` | Red Hat:enterprise_linux:8::baseos | All versions | 2:8.0.1763-24.el8_10 |
| `vim-minimal` | Red Hat:enterprise_linux:8::baseos | All versions | 2:8.0.1763-24.el8_10 |
| `vim-X11` | Red Hat:enterprise_linux:9::appstream | All versions | 2:8.2.2637-26.el9_8.6 |
| `vim-enhanced` | Red Hat:enterprise_linux:9::appstream | All versions | 2:8.2.2637-26.el9_8.6 |
| `vim` | Red Hat:enterprise_linux:9::baseos | All versions | 2:8.2.2637-26.el9_8.6 |
| `vim-minimal` | Red Hat:enterprise_linux:9::baseos | All versions | 2:8.2.2637-26.el9_8.6 |
| `vim` | Rocky Linux:10 | All versions | 2:9.1.083-9.el10_2.4 |
| `vim` | Rocky Linux:8 | All versions | 2:8.0.1763-24.el8_10 |
| `vim` | Rocky Linux:9 | All versions | 2:8.2.2637-26.el9_8.6 |

Products: Vim Vim.

## How do I fix CVE-2026-41411?

Upgrade to a fixed version.

## Is CVE-2026-41411 being exploited?

There is no known exploitation of CVE-2026-41411 in the wild and no public exploit code.

## Other vulnerabilities in Vim Vim

- [CVE-2020-20703](https://insights.sbomify.com/CVE-2020-20703/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-6349](https://insights.sbomify.com/CVE-2017-6349/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-6350](https://insights.sbomify.com/CVE-2017-6350/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-5953](https://insights.sbomify.com/CVE-2017-5953/): Integer overflow in n/a (critical 9.8)
- [CVE-2008-3075](https://insights.sbomify.com/CVE-2008-3075/): Command injection in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41411 and fix it if it is affected.

What it is: CVE-2026-41411 is a medium-severity command injection vulnerability in Vim Vim, published on 24 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-41411 in the wild and no public exploit code.

Affected product: Vim Vim. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41411/ (Markdown: https://insights.sbomify.com/CVE-2026-41411/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41411
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41411
- OSV: https://osv.dev/vulnerability/CVE-2026-41411

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41411/
Summaries are generated and may contain mistakes; the official description above is the record.