CVE-2026-111451: OS Command Injection
Wheels CLI 4.0.0 through 4.1.1 insufficiently validates or escapes caller-supplied values and package contents. Deploy release/version/rollback values can execute shell commands on deploy hosts as the SSH user and on the CI runner during builds. Package removal and destroy paths can delete unintended files; package extraction can overwrite other vendor files; generator names can write outside the project or inject executable CFML into generated code. Inputs may originate from CI variables, branch names, packages or an AI agent using the CLI's MCP tools. Also relevant are unencoded display properties in generated scaffold show views since 4.1.0 and in generated admin views, permitting stored XSS, and stale process-ID handling in RustCFML server commands that can terminate an unrelated process. This is fixed in 4.1.2; existing affected generated views also require the documented edit.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Wheels CLIto a version that resolves this vulnerability.Fixed in 4.1.2
Event History
Frequently Asked Questions
Which environments are most exposed?
Deploy hosts and CI runners are exposed when they run affected Wheels CLI versions with caller-supplied deploy, release, version, or rollback values. Projects using package installation, removal, extraction, destroy, or generator commands are also affected by file overwrite, deletion, path traversal, or generated-code injection risks.
What attacker-controlled inputs can trigger the issue?
Relevant inputs can come from CI variables, branch names, package contents, or an AI agent using the CLI MCP tools. Exploitation of the command-injection paths requires an attacker to influence the applicable CLI values or package data and have the affected command run.
Are generated application views affected after upgrading the CLI?
Existing generated scaffold show views created since 4.1.0 and generated admin views may retain stored XSS issues after the CLI is upgraded. These existing views require the documented edit in addition to upgrading to 4.1.2.
What should teams do if they cannot patch immediately?
Do not run affected deploy, release, version, rollback, package, destroy, extraction, or generator operations with untrusted CI variables, branch names, package contents, or MCP-tool input. Restrict who and what can supply those values, and treat CI runners and deploy hosts as potentially exposed because commands execute as the CI runner or SSH user.
What is the remediation version?
The issue is fixed in Wheels CLI 4.1.2. Affected versions are 4.0.0 through 4.1.1.