Composer: Multiple Vulnerabilities — GLSA 202508-06

Multiple vulnerabilities have been discovered in Composer, the worst of which can lead to arbitrary code execution.

Affected packages

dev-php/composer on all architectures
Affected versions <= 9999
Unaffected versions

Background

Composer is a dependency manager for the PHP programming language.

Description

Integrators using Composer code to call `VcsDriver::getFileContent` can have a code injection vulnerability if the user can control the `$file` or `$identifier` argument. This leads to a vulnerability on packagist.org for example where the composer.json's `readme` field can be used as a vector for injecting parameters into hg/Mercurial via the `$file` argument, or git via the `$identifier` argument if you allow arbitrary data there (Packagist does not, but maybe other integrators do). Composer itself should not be affected by the vulnerability as it does not call `getFileContent` with arbitrary data into `$file`/`$identifier`.

Impact

Please review the referenced CVE identifiers for details.

Workaround

There is no known workaround at this time.

Resolution

Gentoo has discontinued support for composer and the package should be removed:

 # emerge --sync
 # emerge --ask --verbose --depclean "dev-php/composer"
 

References

Release date
August 06, 2025

Latest revision
August 06, 2025: 1

Severity
normal

Exploitable
local and remote

Bugzilla entries