Local command execution via shell-interpolated package names
Published Mar 16, 2026 · Updated Mar 16, 2026
Command injection in MCP Code Executor 0.3.0 and earlier allows local users to execute commands through crafted dependency package names. The installDependencies function joins the packages array into shell command strings for conda, pip, or uv and passes them to child_process.exec. Access to the install_dependencies MCP tool is required, and injected commands run with the MCP server process's privileges.
Summary
What happened
Command injection in MCP Code Executor 0.3.0 and earlier allows local users to execute commands through crafted dependency package names. The installDependencies function joins the packages array into shell command strings for conda, pip, or uv and passes them to child_process.exec. Access to the install_dependencies MCP tool is required, and injected commands run with the MCP server process's privileges.
The record
- CVE
- CVE-2026-4199
- Published
- Mar 16, 2026
- Updated
- Mar 16, 2026
- Vendor
- bazinga012
- Product
- MCP Code Executor
- Classifications
- CWE-74, CWE-77, T1059
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 16, 2026CVE publishedPublication date reported by the CVE source.
- Mar 16, 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=0.1
- Affected versionversion=0.2
- Affected versionversion=0.3.0
What conditions does exploitation require?
What is affected?
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
- GitHub issue #17 proof of conceptproof of concept · unverified
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