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

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.

Published: 2026-04-24 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-41411 is rated Moderate Risk (40.3/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.50%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-41411

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.13% 0.50% +0.37%
2 2026-04-28 0.17% 0.13% -0.04%
3 2026-04-27 — 0.17% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-41411

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.6 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.8 4.7 [email protected]

Weakness enumeration for CVE-2026-41411

OS Trackers for CVE-2026-41411

vendor priority summary link
debian not yet assigned CVE-2026-41411 not yet assigned priority: Debian including 1 source packages (vim), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2026-41411
suse medium — https://www.suse.com/security/cve/CVE-2026-41411/
ubuntu medium CVE-2026-41411 medium priority: Ubuntu including 1 source packages (vim), 9 status rows across 9 suites (bionic, focal, jammy, noble, questing, resolute, trusty, upstream, xenial): needed 4, released 4, needs-triage 1. https://ubuntu.com/security/CVE-2026-41411

Affected software / configurations for CVE-2026-41411

Vendor Product Version Raw CPE
vim vim < 9.2.0357 cpe:2.3:a:vim:vim:*:*:*:*:*:*:*:*

References for CVE-2026-41411

cvelogic Threat Intelligence