Composer
This hub aggregates every CVE we track for Composer, a product in the oss libraries space. Use it to gauge the current risk picture and drill into individual advisories.
21
CVEs tracked
0
Critical
12
High
0
In CISA KEV
Severity distribution
HIGH12MEDIUM8
Monthly trend
0
0
0
0
0
0
0
1
0
0
0
0
0
0
1
0
0
0
2
0
1
5
0
2
2024-102026-09
Latest CVEs
The 15 most recently published vulnerabilities affecting Composer.
- CVE-2026-59944Composer: CVE-2026-59946 fix bypass via symlinked package bin path6.1
- CVE-2026-84361Composer: Perforce source URL permits P4PORT `rsh:` command execution
- CVE-2026-45793Composer: Github Actions issued GITHUB_TOKEN disclosure in GitHub Actions logs7.5
- CVE-2026-11914Composer - Critical - Unsupported - SA-CONTRIB-2026-0465.9
- CVE-2026-59947Composer: URL-embedded HTTP-Basic username leaks to verbose logs (GitHub PAT exposure)4.7
- CVE-2026-59948Composer: Arbitrary file write outside vendor via malicious transitive package name7.0
- CVE-2026-59946Composer: Path traversal in package bin field lets dependencies chmod arbitrary host files6.1
- CVE-2026-10043MosaicML Composer Deserialization of Untrusted Data Remote Code Execution Vulnerability7.8
- CVE-2026-40261Composer has Command Injection via Malicious Perforce Reference8.8
- CVE-2026-40176Composer is vulnerable to Command Injection via Malicious Perforce Repository7.8
- CVE-2025-67746Composer vulnerable to ANSI sequence injection4.3
- CVE-2025-3510tagDiv Composer <= 5.4 - Authenticated (Contributor+) Stored Cross-Site Scripting via Multiple Shortcodes6.4
- 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
Product normalization is registry-driven with AI assist and human review. How it works