Composer
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 1.0, < 2.2.30
- >= 2.3.0, < 2.10.3
Fixed in 2.2.30, 2.10.3
Mitigation
Upgrade composer to 2.2.30 or 2.10.3 or later.
References
- Vendor advisory github.com/composer/composer/security/advisori…
- Patch github.com/composer/composer/commit/0aac50528e…
- Patch github.com/composer/composer/commit/199ad81a9c…
2 more
- Release notes github.com/composer/composer/releases/tag/2.10…
- Release notes github.com/composer/composer/releases/tag/2.2.…
Timeline
Days relative to CVE publicationFirst public PoC 9 h after publication; not in CISA KEV. First PoC: Saku0512/CVE-2026-84361-poc (created 2 Sep 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| Saku0512/CVE-2026-84361-poc | 2 Sep 2026 +9 h | 0 | PoC
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.