composer/composer
Affected
- introduced
2.3.0, fixed2.9.6(ecosystem)
Fixed versions
2.9.6
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: BIT-composer-2026-40176, CVE-2026-40176
Composer has a command injection via malicious perforce repository
Impact
The Perforce::generateP4Command() method constructed shell commands by interpolating user-supplied Perforce connection parameters (port, user, client) without proper escaping. An attacker controlling a repository configuration in a malicious composer.json declaring a Perforce VCS repository could inject arbitrary commands through these values, leading to command execution in the context of the user running Composer. Composer would execute these injected commands even if Perforce is not installed.
VCS repositories are only loaded from the root composer.json file located in the directory you execute Composer commands in and from the composer config directory (e.g. ~/.config/composer/composer.json). So this vulnerability cannot be exploited through composer.json files of packages installed as dependencies.
You are at risk of command execution if you run Composer commands on untrusted projects with attacker supplied composer.json files, regardless of whether you or any of your dependencies use Perforce.
Patches
Fixed in Composer 2.2.27 (2.2 LTS) and 2.9.6 (mainline)
Workarounds
High Basis: The source's own band: HIGH
2.3.0, fixed 2.9.6 (ecosystem)2.9.6
The export has no generic command for this ecosystem.
1.0.0, fixed 2.2.27 (ecosystem)2.2.27
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0