macvim-dev / macvim-dev/macvim
[Security] MacVim affected by CVE-2026-41411 — tag file command injection (vim < 9.2.0357)
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- Vim Script
- Estrellas
- 7.9k
- Forks
- 691
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
[Security] MacVim affected by CVE-2026-41411 — tag file command injection (vim < 9.2.0357)
Summary
MacVim bundles the vim source at version 9.2 (patches 1-332 in the current build), which is
below the patched version 9.2.0357 that fixes CVE-2026-41411.
Vulnerability Details
- Upstream CVE: CVE-2026-41411
- Inherited from:
vim/vim - Affected code: tag file processing (wildcard expansion of filename fields)
- Vulnerability type: CWE-78 — OS Command Injection
- Fixed in: vim 9.2.0357 (commit
c78194e41d5a0b05b0ddf383b6679b1503f977fb)
Root Cause
Prior to vim 9.2.0357, when resolving a tag, the filename field from the tags file is passed
through wildcard expansion to resolve environment variables and wildcards. If a crafted tags
file contains a filename with shell metacharacters or backtick-enclosed commands, those
commands are executed when the tag is resolved.
An attacker who can influence the tags file (e.g., via a malicious project or downloaded
code repository) can achieve arbitrary command execution when the victim opens a file and
navigates to a tag definition.
Affected MacVim Version
MacVim r183 (vim 9.2 patches 1-332) — current HEAD as of 2026-05-18.
The fix commit c78194e41d5a0b05b0ddf383b6679b1503f977fb from vim/vim is not present
in the macvim-dev/macvim repository:
git log --all --oneline | grep c78194e # returns no output
Suggested Fix
Merge or cherry-pick vim/vim patches up to at least 9.2.0357:
References
- CVE: https://nvd.nist.gov/vuln/detail/CVE-2026-41411
- Upstream advisory: https://github.com/vim/vim/security/advisories/GHSA-7rvw-9w8x-xhwx
- Upstream fix commit: https://github.com/vim/vim/commit/c78194e41d5a0b05b0ddf383b6679b1503f977fb
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Comienza inspeccionando el código fuente de Vim incluido y su historial; después compara el repositorio con el commit upstream c78194e41d5a0b05b0ddf383b6679b1503f977fb; el issue indica que git log actualmente no encuentra ningún commit coincidente. Actualiza los parches de Vim incluidos a, como mínimo, 9.2.0357 y verifica que la compilación de MacVim incorpore la corrección de seguridad upstream para tag-file.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- macos, vim
- Área
- desktop, security
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 55/100