Command Injection Affecting composer/composer package, versions >=1.0, <2.2.30>=2.3.0, <2.10.3
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-PHP-COMPOSERCOMPOSER-20186765
- published28 Sept 2026
- disclosed8 Sept 2026
- creditSaku0512
Introduced: 8 Sep 2026
NewCVE-2026-84361 (opens in a new tab)How to fix?
Upgrade composer/composer to version 2.2.30, 2.10.3 or higher.
Overview
composer/composer is a Dependency Manager for PHP. Composer helps you declare, manage and install dependencies of PHP projects. It ensures you have the right stack everywhere.
Affected versions of this package are vulnerable to Command Injection via the handling of Perforce source addresses when invoking the p4 client. An attacker can execute arbitrary commands with the privileges of the user or CI account running the process by supplying a malicious Perforce source URL in a package's metadata. This is only exploitable if the p4 Perforce CLI client is installed and present in the system's PATH, the attacker can control a package's source section with a perforce type from a non-Packagist repository or untrusted lock file, and the package is installed from source (such as with --prefer-source).