Composer: Perforce source URL permits P4PORT `rsh:` command execution
Composer is a dependency Manager for the PHP language. From 1.0 until 2.2.30 and 2.10.3, a malicious dependency package from a custom Composer repository or an untrusted composer.lock file could set source.type to perforce and source.url to an rsh: or jsh: P4PORT value. When the Perforce p4 client was installed and Composer installed the package from source through composer install or composer update, including --prefer-source, Composer\Util\Perforce passed the address to p4 without validation, causing p4 to run a local command with the privileges of the user or CI account. Packagist.org does not permit Perforce source metadata. This issue is fixed in versions 2.2.30 and 2.10.3.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-84361US | — | Exploit | ||
Composer is a dependency Manager for the PHP language. From 1.0 until 2.2.30 and 2.10.3, a malicious dependency package from a custom Composer repository or an untrusted composer.l… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/composer/composer/commit/0aac50528e83ed635cf788333635897469440220WEB
- https://github.com/composer/composer/commit/199ad81a9cc6a2a5164ad79a8da26b2e19e521afWEB
- https://github.com/composer/composer/releases/tag/2.10.3WEB
- https://github.com/composer/composer/releases/tag/2.2.30WEB
- https://github.com/composer/composer/security/advisories/GHSA-rvx4-ffvw-m9q3WEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-84361WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan