CVE-2026-40261

Composer has Command Injection via Malicious Perforce Reference

Published Apr 15, 2026 CVSS 3.1 · 8.8 High EPSS 1.7% KEV · Not listed
Description
Composer is a dependency manager for PHP. Versions 1.0 through 2.2.26 and 2.3 through 2.9.5 contain a command injection vulnerability in the Perforce::syncCodeBase() method, which appends the $sourceReference parameter to a shell command without proper escaping, and additionally in the Perforce::generateP4Command() method as in GHSA-wg36-wvj6-r67p / CVE-2026-40176, which interpolates user-supplied Perforce connection parameters (port, user, client) from the source url field without proper escaping. An attacker can inject arbitrary commands through crafted source reference or source url values containing shell metacharacters, even if Perforce is not installed. Unlike CVE-2026-40176, the source reference and url are provided as part of package metadata, meaning any compromised or malicious Composer repository can serve package metadata declaring perforce as a source type with malicious values. This vulnerability is exploitable when installing or updating dependencies from source, including the default behavior when installing dev-prefixed versions. This issue has been fixed in Composer 2.2.27 (2.2 LTS) and 2.9.6 (mainline). If developers are unable to immediately update, they can avoid installing dependencies from source by using --prefer-dist or the preferred-install: dist config setting, and only use trusted Composer repositories as a workaround.

Analysis

AI-generated

Technical impact

Composer, the PHP dependency manager, has a command injection flaw in the Perforce::syncCodeBase() and Perforce::generateP4Command() methods. The library appends a user‑supplied source reference and connection parameters directly into shell commands without escaping. An attacker can therefore inject arbitrary shell commands through crafted metadata fields in a Composer repository, even if Perforce is not installed. This vulnerability affects package installation and updating, including the default handling of dev‑prefixed versions, and allows an attacker who controls the package metadata to execute arbitrary code on the host system.

Affected Systems

Vulnerable Composer releases include versions 1.0 through 2.2.26 and 2.3 through 2.9.5. The issue is fixed in Composer 2.2.27 (LTS) and 2.9.6 (mainline).

Risk and Exploitability

The CVSS score of 8.8 signals a high‑severity flaw. The EPSS score of 1% indicates a low but non‑zero probability of exploitation. Exploitation requires only that a malicious or compromised Composer repository is used; no additional software needs to be present. The vulnerability is actively exploitable during normal dependency installation, making it a direct and realistic threat in environments that rely on untrusted repositories or public packages.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Composer to at least version 2.2.27 or 2.9.6 to apply the vendor fix.
  • When installing or updating, run Composer with the --prefer-dist flag or set preferred-install to dist so that dependencies are not built from source.
  • Only use trusted Composer repositories to reduce the risk of malicious package metadata.

Generated by OpenCVE AI on June 18, 2026 at 09:02 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-gqw4-4w2p-838q Composer has a command injection via malicious perforce reference
History
Type Values Removed Values Added
CPEs cpe:2.3:a:getcomposer:composer:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Getcomposer
Getcomposer composer
Vendors & Products Getcomposer
Getcomposer composer
Type Values Removed Values Added
Description Composer is a dependency manager for PHP. Versions 1.0 through 2.2.26 and 2.3 through 2.9.5 contain a command injection vulnerability in the Perforce::syncCodeBase() method, which appends the $sourceReference parameter to a shell command without proper escaping, and additionally in the Perforce::generateP4Command() method as in GHSA-wg36-wvj6-r67p / CVE-2026-40176, which interpolates user-supplied Perforce connection parameters (port, user, client) from the source url field without proper escaping. An attacker can inject arbitrary commands through crafted source reference or source url values containing shell metacharacters, even if Perforce is not installed. Unlike CVE-2026-40176, the source reference and url are provided as part of package metadata, meaning any compromised or malicious Composer repository can serve package metadata declaring perforce as a source type with malicious values. This vulnerability is exploitable when installing or updating dependencies from source, including the default behavior when installing dev-prefixed versions. This issue has been fixed in Composer 2.2.27 (2.2 LTS) and 2.9.6 (mainline). If developers are unable to immediately update, they can avoid installing dependencies from source by using --prefer-dist or the preferred-install: dist config setting, and only use trusted Composer repositories as a workaround.
Title Composer has Command Injection via Malicious Perforce Reference
Weaknesses CWE-20
CWE-78
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-20

    Improper Input Validation

  • CWE-78

    Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 15, 2026, 1:01 AM
Reserved
Apr 10, 2026, 5:31 PM
Status
Modified
Published
Apr 15, 2026, 9:17 PM
Modified
Jul 15, 2026, 2:21 AM
Severity
Important
Public date
Apr 15, 2026, 8:56 PM