CVE-2026-84361: Composer arbitrary command execution via a malicious package's Perforce source URL
Summary If the p4 Perforce CLI client is installed, a malicious dependency package from a package repository allowing arbitrary perforce source URLs (packagist.org is safe) could execute arbitrary commands when running composer install or composer update. Composer passed a package's Perforce source address to the p4 CLI client without validating it.
Published Sep 8, 2026
Affected packages
composer/composer
- Ecosystem
- Composer (PHP)
- Affected
- >= 2.3.0, < 2.10.3
- Fixed in
- 2.10.3
- Check
composer show composer/composer
composer/composer
- Ecosystem
- Composer (PHP)
- Affected
- >= 1.0, < 2.2.30
- Fixed in
- 2.2.30
- Check
composer show composer/composer
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
If the p4 Perforce CLI client is installed, a malicious dependency package from a package repository allowing arbitrary perforce source URLs (packagist.org is safe) could execute arbitrary commands when running composer install or composer update. Composer passed a package's Perforce source address to the p4 CLI client without validating it. The p4 CLI client accepts addresses that mean "run this local command" instead of "connect to this server". This is remote code execution with the privileges of the user or CI account running Composer.
Am I affected?
You are only affected if all of the following are true:
- The Perforce
p4command line client is installed and on thePATHof the machine running Composer. - An attacker can control a package metadata's
sourcesection with a perforce type. Packagist.org does not allow perforce source metadata, so you are only exploitable if you rely on another Composer repository (any customcomposer-type repository, or an inlinepackagerepository entry), or acomposer.lockfile you obtained from somewhere you do not trust. - The package gets installed from source, either because it has no dist artifact or because source installs are selected (for example
--prefer-source).
Plainly not affected: anyone without the p4 client installed, which is the large majority of Composer users. Perforce is an optional VCS integration. Also not affected: projects that only consume packages from Packagist.org, which does not allow Perforce source repositories and therefore cannot serve a package with a Perforce source address.
Most realistic way to get hit: a developer workstation or CI image that has Perforce tooling installed, pulling packages from a private or third party Composer repository that an attacker has compromised.
Patched versions
Composer now validates Perforce source addresses before handing them to the p4 client, and accepts only real network endpoints (an optional tcp/ssl transport with a host and port). Addresses that make the client spawn a local process are rejected, and the package fails validation on both update and install, before any p4 command runs. Fixed in Composer 2.10.3 and 2.2.30.
Note: If you legitimately use Perforce with an unusual P4PORT value that is not a plain host and port, Composer will now reject it.
Workarounds
Upgrading is the only complete fix.
Risk reduction short of upgrading:
- Remove the
p4client from thePATHof machines that run Composer but do not use Perforce. This fully blocks this specific attack, since the vulnerability depends on that client being present. - Restrict configured repositories to sources you control or trust, and treat lock files from untrusted sources as untrusted input.
Credited to Saku0512.
References
- https://github.com/composer/composer/security/advisories/GHSA-rvx4-ffvw-m9q3
- https://nvd.nist.gov/vuln/detail/CVE-2026-84361
- https://github.com/composer/composer/commit/0aac50528e83ed635cf788333635897469440220
- https://github.com/composer/composer/commit/199ad81a9cc6a2a5164ad79a8da26b2e19e521af
- https://github.com/composer/composer/releases/tag/2.10.3
- https://github.com/composer/composer/releases/tag/2.2.30
- https://github.com/advisories/GHSA-rvx4-ffvw-m9q3
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-59944
Composer: GHSA-gjfg-22fp-rrxx fix bypass via symlinked package bin path
medium6.1Oct 2, 2026CVE-2026-59946
Composer: Path traversal in package bin field lets dependencies chmod arbitrary host files
medium6.1Jul 20, 2026CVE-2026-59947
Composer: URL-embedded HTTP-Basic username leaks to verbose logs (GitHub PAT exposure)
medium4.7Jul 20, 2026CVE-2026-59948
Composer: Arbitrary file write outside vendor via malicious transitive package name
high7.0Jul 20, 2026CVE-2026-45793
Github Actions issued GITHUB_TOKEN disclosure in GitHub Actions logs
high7.5May 19, 2026CVE-2026-40176
Composer has a command injection via malicious perforce repository
high7.8Apr 14, 2026
