Composer/composer
9 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Composer/composer, a product in the oss libraries space. Use it to gauge the current risk picture and drill into individual advisories.
Composer/composer CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 1 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 0 |
| 2026-04 | 0 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 0 |
Severity
How the 9 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- High7
- Medium2
Latest CVEs
The 9 most recently published vulnerabilities affecting Composer/composer.
- CVE-2025-67746Composer vulnerable to ANSI sequence injection4.3
- CVE-2024-35242Composer vulnerable to command injection via malicious git/hg branch names8.8
- CVE-2024-35241Composer vulnerable to command injection via malicious git branch name8.8
- CVE-2024-24821Code execution and possible privilege escalation via compromised InstalledVersions.php or installed.php in Composer8.8
- CVE-2023-43655Remote Code Execution via web-accessible composer.phar6.4
- CVE-2015-8371Composer before 2016-02-10 allows cache poisoning from other projects built on the same host. This results in attacker-controlled code entering a server-side build process. The issue occurs because...8.8
- CVE-2022-24828Missing input validation can lead to command execution in composer8.3
- CVE-2021-41116Command injection in composer on Windows8.2
- CVE-2021-29472Missing argument delimiter can lead to code execution via VCS repository URLs or source download URLs on systems with Mercurial in composer8.8
Product grouping is registry-driven, with AI assist and human review. How it works