Technology · Packagist
composer/composer (Packagist) vulnerabilities
Updated . Rebuilt every hour.
Junglewise Threat Intelligence has tracked 17 vulnerabilities in composer/composer (Packagist): 0 in the last 7 days and 2 in the last 90 days, 0 of them critical and 0 exploited in the wild. The most recent, CVE-2026-59944, was published on 16 September 2026. Nothing in the last four weeks, down from 1 vulnerability in the four before.
- Last 7 days
- 0
- Last 90 days
- 2
- Critical, all time
- 0
- Exploited in the wild
- 0
About composer/composer (Packagist)
Dependency manager for PHP that resolves and installs project dependencies.
Latest composer/composer (Packagist) vulnerabilities
- CVE-2026-59944: Composer bin path validation bypass via symlinksmediumCVSS 6.1EPSS 0.3%
- CVE-2026-84361: Composer arbitrary command execution via malicious Perforce source URLhighCVSS 4EPSS 0.5%
- CVE-2026-45793: Composer sensitive information disclosure in GitHub token validationhighCVSS 7.5EPSS 1.0%
- CVE-2026-59948: Composer path traversal via malicious package namehighCVSS 7EPSS 0.2%
- CVE-2026-59947: Composer sensitive information disclosure in verbose debug outputmediumCVSS 4.7EPSS 0.1%
- CVE-2026-59946: Composer path traversal in package bin fieldmediumCVSS 6.1EPSS 0.2%
- CVE-2026-40261: Composer command injection in Perforce repository handlinghighCVSS 8.8EPSS 1.9%
- CVE-2026-40176: Composer command injection in Perforce repository handlinghighCVSS 7.8EPSS 1.0%
- CVE-2025-67746: Composer is vulnerable to ANSI sequence injectionmediumCVSS 4EPSS 0.4%
- CVE-2024-35241: Composer has a command injection via malicious git branch namelowCVSS 3.1EPSS 1.1%
- CVE-2024-35242: Composer has multiple command injections via malicious git/hg branch nameslowCVSS 3.1EPSS 3.3%
- CVE-2024-24821: Composer code execution and possible privilege escalation via compromised InstalledVersions.php or installed.phplowCVSS 3.1EPSS 0.3%
- CVE-2023-43655: Composer Remote Code Execution vulnerability via web-accessible composer.pharlowCVSS 3.1EPSS 1.4%
- CVE-2015-8371: Composer allows cache poisoning from other projects built on the same hostlowCVSS 3.1EPSS 0.7%
- CVE-2022-24828: Missing input validation can lead to command execution in composerlowCVSS 3.1EPSS 1.9%
- CVE-2021-41116: Improper escaping of command arguments on Windows leading to command injectionlowCVSS 3.1EPSS 2.9%
- CVE-2021-29472: Composer's missing argument delimiter can lead to code execution via VCS repository URLs or source download URLs on…lowCVSS 3.1EPSS 4.6%
Most severe composer/composer (Packagist) vulnerabilities
Exploited in the wild first, then by severity and CVSS score.
- CVE-2026-40261: Composer command injection in Perforce repository handlinghighCVSS 8.8EPSS 1.9%
- CVE-2026-40176: Composer command injection in Perforce repository handlinghighCVSS 7.8EPSS 1.0%
- CVE-2026-45793: Composer sensitive information disclosure in GitHub token validationhighCVSS 7.5EPSS 1.0%
- CVE-2026-59948: Composer path traversal via malicious package namehighCVSS 7EPSS 0.2%
- CVE-2026-84361: Composer arbitrary command execution via malicious Perforce source URLhighCVSS 4EPSS 0.5%
- CVE-2026-59944: Composer bin path validation bypass via symlinksmediumCVSS 6.1EPSS 0.3%
- CVE-2026-59946: Composer path traversal in package bin fieldmediumCVSS 6.1EPSS 0.2%
- CVE-2026-59947: Composer sensitive information disclosure in verbose debug outputmediumCVSS 4.7EPSS 0.1%
- CVE-2025-67746: Composer is vulnerable to ANSI sequence injectionmediumCVSS 4EPSS 0.4%
- CVE-2021-29472: Composer's missing argument delimiter can lead to code execution via VCS repository URLs or source download URLs on…lowCVSS 3.1EPSS 4.6%
Vulnerabilities per week
Nothing in the last four weeks, down from 1 vulnerability in the four before. The last 13 weeks, by the week each vulnerability was published.
| Week of | Bar | Vulns | Critical |
|---|---|---|---|
| 17 Aug 2026 | 0 | 0 | |
| 24 Aug 2026 | 0 | 0 | |
| 31 Aug 2026 | 1 | 0 | |
| 7 Sep 2026 | 0 | 0 | |
| 14 Sep 2026 | 1 | 0 | |
| 21 Sep 2026 | 0 | 0 | |
| 28 Sep 2026 | 0 | 0 | |
| 5 Oct 2026 | 0 | 0 | |
| 12 Oct 2026 | 0 | 0 | |
| 19 Oct 2026 | 0 | 0 | |
| 26 Oct 2026 | 0 | 0 | |
| 2 Nov 2026 | 0 | 0 | |
| 9 Nov 2026 | 0 | 0 |
Embed a badge
A live badge for a README, a status page or an internal wiki: how many composer/composer (Packagist) vulnerabilities were published in the last 7 days and how many of them are critical, refreshed hourly.
[](https://junglewise.ai/threats/technologies/composer-composer)<a href="https://junglewise.ai/threats/technologies/composer-composer"><img src="https://junglewise.ai/threats/technologies/composer-composer/badge.svg" alt="composer/composer (Packagist) vulnerabilities" /></a>How this is built
Junglewise Threat Intelligence collects vulnerabilities from NVD, GitHub Security Advisories, OSV, the CISA Known Exploited Vulnerabilities catalog, FIRST EPSS and vendor advisories, and matches each one to the technologies and vendors it affects. Dates are the date a vulnerability was published, in UTC.
The pages are rebuilt from the database every hour. Frozen weekly and monthly reports never change once published, so they can be cited.
Use this data
The same data is at https://junglewise.ai/threats/technologies/composer-composer.json, and this page as text at https://junglewise.ai/threats/technologies/composer-composer.md, for scripts and language models. It is free to reuse under CC BY 4.0 with a link back to this page.
Cite as: Junglewise Threat Intelligence, "composer/composer (Packagist) vulnerabilities", https://junglewise.ai/threats/technologies/composer-composer, 9 November 2026.