Arbitrary command execution via unescaped Ruby regex
Published Jun 11, 2026 · Updated Jun 11, 2026
Code injection in Vim's cucumber filetype plugin before 9.2.0496 allows context-dependent attackers to execute commands via crafted step patterns. The s:stepmatch() function concatenates regex text from repository .rb files into a Ruby Kernel.eval expression without neutralizing a closing slash and appended statements. Execution requires a +ruby build, an attacker-controlled cucumber-style repository, and a user who invokes [d or ]d; commands run with that user's privileges.
Summary
What happened
Code injection in Vim's cucumber filetype plugin before 9.2.0496 allows context-dependent attackers to execute commands via crafted step patterns. The s:stepmatch() function concatenates regex text from repository .rb files into a Ruby Kernel.eval expression without neutralizing a closing slash and appended statements. Execution requires a +ruby build, an attacker-controlled cucumber-style repository, and a user who invokes [d or ]d; commands run with that user's privileges.
The record
- CVE
- CVE-2026-47167
- Published
- Jun 11, 2026
- Updated
- Jun 11, 2026
- Vendor
- Vim
- Product
- Vim
- Classifications
- CWE-94, CWE-95, T1204.002, T1059
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 2026CVE publishedPublication date reported by the CVE source.
- Jun 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 9.2.0496
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream cucumber code-injection regression proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo