Bug 2458828 (CVE-2026-40176) - CVE-2026-40176 composer: command injection via malicious Perforce repository definition
Summary: CVE-2026-40176 composer: command injection via malicious Perforce repository ...
Keywords:
Status: NEW
Alias: CVE-2026-40176
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2459010 2459011
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-04-15 21:01 UTC by OSIDB Bzimport
Modified: 2026-04-16 18:53 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-04-15 21:01:11 UTC
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::generateP4Command() method, which constructs shell commands by interpolating user-supplied Perforce connection parameters (port, user, client) without proper escaping. An attacker can inject arbitrary commands through these values in a malicious composer.json declaring a Perforce VCS repository, leading to command execution in the context of the user running Composer, even if Perforce is not installed. VCS repositories are only loaded from the root composer.json or the composer config directory, so this cannot be exploited through composer.json files of packages installed as dependencies. Users are at risk if they run Composer commands on untrusted projects with attacker-supplied composer.json files. This issue has been fixed in Composer 2.2.27 (2.2 LTS) and 2.9.6 (mainline).


Note You need to log in before you can comment on or make changes to this bug.