HIGH8.8CVE-2026-40261Composer has Command Injection via Malicious Perforce Reference >= 2.3.0, < 2.9.6
HIGH8.8CVE-2024-35241Composer vulnerable to command injection via malicious git branch name >= 2.0, < 2.2.24
HIGH8.8CVE-2024-35242Composer vulnerable to command injection via malicious git/hg branch names >= 2.0, < 2.2.24
HIGH8.8Code execution and possible privilege escalation via compromised InstalledVersions.php or installed.php in Composer
>= 2.0.0-alpha1, < 2.2.23
HIGH8.8Remote Code Execution via web-accessible composer.phar
from 0, < 1.10.27
HIGH8.8Composer allows cache poisoning from other projects built on the same host
from 0, < 1.0.0
HIGH8.8Missing argument delimiter can lead to code execution via VCS repository URLs or source download URLs on systems with Mercurial in composer
from 0, < 1.10.22
HIGH8.3Missing input validation can lead to command execution in composer
from 0, < 1.10.26
HIGH8.2Command injection in composer on Windows
from 0, < 1.10.23
HIGH7.8Composer is vulnerable to Command Injection via Malicious Perforce Repository
>= 2.3.0, < 2.9.6
HIGH7.5Github Actions issued GITHUB_TOKEN disclosure in GitHub Actions logs
>= 2.3.0, < 2.9.8
HIGH7.0Composer: Arbitrary file write outside vendor via malicious transitive package name
>= 2.3.0, < 2.10.2
MEDIUM6.1Composer: Path traversal in package bin field lets dependencies chmod arbitrary host files
>= 2.3.0, < 2.10.2
MEDIUM4.7Composer: URL-embedded HTTP-Basic username leaks to verbose logs (GitHub PAT exposure)
>= 2.3.0, < 2.10.2
MEDIUM4.3Composer vulnerable to ANSI sequence injection
>= 2.0.0, < 2.2.26