CVE-2026-41411

MEDIUMNVD 6.66.6—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.6 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 59% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 6.6Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
6.6
EG Score
6.6(medium)
EG Risk
30(Track)
EG Risk 30/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity66% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
41%
KEV
Not listed

Published

April 24, 2026

Last Modified

April 27, 2026

Advisory Details (2)

Auto-updated Jun 14, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Command injection via backtick expansion in tag filenames in Vim < v9.2.0357 · Advisory · vim/vim · GitHub

https://github.com/vim/vim/security/advisories/GHSA-cwgx-gcj7-6qh8
github_commit

commit c78194e41d5a (vim/vim)

Fix landed in vim/vim commit c78194e41d5a — awaiting tagged release

https://github.com/vim/vim/commit/c78194e41d5a0b05b0ddf383b6679b1503f977fb

Vendor Advisories for CVE-2026-41411(17)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(15)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhui5/rhua-rhel9:17847950762026-07-23redhat
redhatinsights-proxy/insights-proxy-container-rhel9:17828905032026-07-01redhat
redhatvim-2:8.0.1763-20.el8_8.22026-07-01redhat
redhatvim-2:8.0.1763-19.el8_6.62026-07-01redhat
redhatvim-2:8.0.1763-15.el8_4.22026-06-30redhat
redhatvim-2:9.1.083-5.el10_0.32026-06-29redhat
redhatdiscovery/discovery-ui-rhel9:17827565412026-06-29redhat
redhatvim-2:8.2.2637-20.el9_2.22026-06-23redhat
redhatvim-2:9.1.083-9.el10_2.42026-06-23redhat
redhatvim-2:8.2.2637-26.el9_8.62026-06-23redhat
redhatvim-2:8.0.1763-24.el8_102026-06-23redhat
redhatvim-2:8.2.2637-20.el9_4.32026-06-22redhat
redhatvim-2:8.2.2637-22.el9_6.32026-06-22redhat
ubuntuvim-tiny (2:7.4.1689-3ubuntu1.5+esm33) @ xenial2026-06-14ubuntu
ubuntuxxd (2:9.1.2141-1ubuntu4.1) @ resolute2026-06-14ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
vim—9.2.0357-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
vim2:8.2.2434-3 ... 2:9.2.0858-1 (63 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
vim2:9.0.1378-2 ... 2:9.2.0858-1 (45 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
vim2:9.1.1230-2 ... 2:9.2.0858-1 (19 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
vim2:9.1.1230-2 ... 2:9.2.0355-1 (14 versions)2:9.2.0428-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 52× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 161 total refreshes for this CVE.

  1. 2026-08-30 19:17 UTCEPSS rescore
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-28 21:41 UTCEPSS rescore
  4. 2026-08-27 14:25 UTCEPSS rescore
  5. 2026-08-26 14:46 UTCEPSS rescore
  6. 2026-08-25 13:49 UTCEPSS rescore
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-19 17:03 UTCEPSS rescore
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-17 14:47 UTCEG score recompute
  13. 2026-08-17 14:47 UTCVendor advisory
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 05:46 UTCEG score recompute
  17. 2026-08-16 05:46 UTCVendor advisory
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 04:06 UTCEG score recompute
  21. 2026-08-14 04:06 UTCVendor advisory
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-12 17:47 UTCEG score recompute
  24. 2026-08-12 17:47 UTCVendor advisory
  25. 2026-08-12 13:51 UTCEPSS rescore
Show 75 more
  1. 2026-08-11 16:41 UTCEG score recompute
  2. 2026-08-11 16:41 UTCVendor advisory
  3. 2026-08-11 13:43 UTCEPSS rescore
  4. 2026-08-11 00:00 UTCEPSS rescore
  5. 2026-08-10 13:41 UTCEG score recompute
  6. 2026-08-10 13:41 UTCVendor advisory
  7. 2026-08-09 13:46 UTCEPSS rescore
  8. 2026-08-09 13:16 UTCEG score recompute
  9. 2026-08-09 13:16 UTCVendor advisory
  10. 2026-08-08 16:37 UTCEPSS rescore
  11. 2026-08-08 12:57 UTCEG score recompute
  12. 2026-08-08 12:57 UTCVendor advisory
  13. 2026-08-07 12:32 UTCEG score recompute
  14. 2026-08-07 12:32 UTCVendor advisory
  15. 2026-08-06 13:46 UTCEPSS rescore
  16. 2026-08-05 22:55 UTCEG score recompute
  17. 2026-08-05 22:55 UTCVendor advisory
  18. 2026-08-05 19:17 UTCEPSS rescore
  19. 2026-08-04 15:10 UTCEPSS rescore
  20. 2026-08-04 10:38 UTCEPSS rescore
  21. 2026-08-03 21:00 UTCEG score recompute
  22. 2026-08-03 21:00 UTCVendor advisory
  23. 2026-08-03 10:36 UTCEPSS rescore
  24. 2026-08-02 11:02 UTCEG score recompute
  25. 2026-08-02 11:02 UTCVendor advisory
  26. 2026-08-02 02:27 UTCEPSS rescore
  27. 2026-08-01 04:16 UTCEPSS rescore
  28. 2026-07-30 16:28 UTCEPSS rescore
  29. 2026-07-30 01:30 UTCEPSS rescore
  30. 2026-07-28 15:36 UTCEPSS rescore
  31. 2026-07-27 14:13 UTCEPSS rescore
  32. 2026-07-26 14:54 UTCEPSS rescore
  33. 2026-07-26 14:54 UTCEPSS rescore
  34. 2026-07-25 14:18 UTCEPSS rescore
  35. 2026-07-24 14:17 UTCEPSS rescore
  36. 2026-07-23 14:18 UTCEPSS rescore
  37. 2026-07-23 03:11 UTCEG score recompute
  38. 2026-07-22 14:08 UTCEPSS rescore
  39. 2026-07-21 15:24 UTCEPSS rescore
  40. 2026-07-20 17:08 UTCEPSS rescore
  41. 2026-07-19 22:38 UTCOSV refresh
  42. 2026-07-19 14:31 UTCEPSS rescore
  43. 2026-07-19 02:29 UTCEPSS rescore
  44. 2026-07-18 10:04 UTCEPSS rescore
  45. 2026-07-16 17:03 UTCEPSS rescore
  46. 2026-07-15 16:57 UTCEPSS rescore
  47. 2026-07-15 16:57 UTCEPSS rescore
  48. 2026-07-15 02:00 UTCEPSS rescore
  49. 2026-07-13 22:30 UTCEPSS rescore
  50. 2026-07-13 06:13 UTCEPSS rescore
  51. 2026-07-13 06:13 UTCEPSS rescore
  52. 2026-07-12 05:46 UTCEPSS rescore
  53. 2026-07-11 08:27 UTCEPSS rescore
  54. 2026-07-09 19:10 UTCEPSS rescore
  55. 2026-07-08 15:15 UTCEPSS rescore
  56. 2026-07-07 13:46 UTCEPSS rescore
  57. 2026-07-06 16:27 UTCEPSS rescore
  58. 2026-07-06 16:27 UTCEPSS rescore
  59. 2026-07-06 02:23 UTCEPSS rescore
  60. 2026-07-06 02:23 UTCEPSS rescore
  61. 2026-07-05 02:30 UTCEPSS rescore
  62. 2026-07-04 06:31 UTCEPSS rescore
  63. 2026-07-01 15:06 UTCEPSS rescore
  64. 2026-06-30 23:22 UTCEPSS rescore
  65. 2026-06-29 14:06 UTCEPSS rescore
  66. 2026-06-28 14:07 UTCEPSS rescore
  67. 2026-06-28 04:56 UTCEPSS rescore
  68. 2026-06-27 03:08 UTCEPSS rescore
  69. 2026-06-25 13:49 UTCEPSS rescore
  70. 2026-06-25 13:49 UTCEPSS rescore
  71. 2026-06-24 14:05 UTCEPSS rescore
  72. 2026-06-23 21:33 UTCEPSS rescore
  73. 2026-06-22 14:25 UTCEPSS rescore
  74. 2026-06-22 14:25 UTCEPSS rescore
  75. 2026-06-21 14:56 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-41411?
CVE-2026-41411 is a medium vulnerability published on April 24, 2026. 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…
When was CVE-2026-41411 disclosed?
CVE-2026-41411 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on April 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41411 actively exploited?
CVE-2026-41411 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 59.2% of all scored CVEs.
What is the CVSS score of CVE-2026-41411?
CVE-2026-41411 has a CVSS v3 base score of 6.6 (NVD).
How do I remediate CVE-2026-41411?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41411, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41411

Explore →

Is Your Infrastructure Affected by CVE-2026-41411?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs