Bug 2527051 (CVE-2026-84361) - CVE-2026-84361 composer: Composer: Arbitrary code execution via malicious Perforce source URL
Summary: CVE-2026-84361 composer: Composer: Arbitrary code execution via malicious Per...
Keywords:
Status: NEW
Alias: CVE-2026-84361
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: 2527243 2527244
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-01 20:21 UTC by OSIDB Bzimport
Modified: 2026-09-02 07:16 UTC (History)
0 users

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


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-01 20:21:29 UTC
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.


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