Two separate Vim command-execution bugs reported on oss-security
First merged summary.
Two distinct Vim command-execution issues were reported; neither post confirms exploitation or a workaround.
Christian Brabandt reported two separate command-execution issues in Vim on the oss-security list. On November 12 he said CSS omni-completion before 9.2.1342 passes an unescaped @import file name from the buffer to glob() in runtime/autoload/csscomplete.vim. That report rates the issue Low, maps it to CWE-78, and says a CVE was requested but not assigned. On November 14 he reported a different issue in runtime/ftplugin/ps1.vim affecting Vim before 9.2.1346, tracked as GHSA-r5v6-q6j8-8qw2. The PowerShell excerpt is truncated, and neither post describes exploitation or a workaround.
- CSS bug is in runtime/autoload/csscomplete.vim before Vim 9.2.1342.
- CSS report rates severity Low and maps the issue to CWE-78.
- A CVE was requested for the CSS issue and was not assigned.
- PowerShell bug is in runtime/ftplugin/ps1.vim before Vim 9.2.1346.
- PowerShell issue is tracked as GHSA-r5v6-q6j8-8qw2.
- Neither post describes exploitation or a workaround.
Timeline
dated events in the reporting · oldest first- Nov 12, 2026CSS omni-completion command execution reported for Vim before 9.2.1342 · oss-security
- Nov 14, 2026PowerShell keyword-lookup issue reported for Vim before 9.2.1346 · oss-security
What each outlet adds
beyond the shared facts- oss-securityCSS path, Low severity, CWE-78, and unassigned CVE request.
- oss-securitySeparate PowerShell path and GHSA-r5v6-q6j8-8qw2; excerpt truncated.
Coverage
oldest first · one row per article · UTCVim before 9.2.1342 can run commands via CSS omni-completion
The CSS completion script passes an unescaped @import file name to glob(); a CVE was requested but not assigned.
Vim before 9.2.1346 allows command execution via PowerShell lookup
The issue is in runtime/ftplugin/ps1.vim and is tracked as GHSA-r5v6-q6j8-8qw2.