Advisory record · GHSA-47f6-5gq3-vx9c

Composer has a command injection via malicious git branch name

CVSS 8.8 HighEPSS 0.011 · 64th percentile

Published by the GitHub Advisory Database at 10 Jun 2024, 21:36 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
composer/composerPackagist>=2.0, <2.2.24 || >=2.3, <2.7.72.2.24, 2.7.7
Identifiers
GHSA-47f6-5gq3-vx9c · BIT-composer-2024-35241 · CVE-2024-35241 · PKSA-s25b-vbmp-jvhh
Weakness (CWE)
CWE-77
Published
10 Jun 2024
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Composer, the PHP dependency manager, is vulnerable in versions from 2.0 up to but not including 2.2.24, and from 2.3 up to but not including 2.7.7. The status, reinstall and remove commands can execute code when packages installed from git sources have specially crafted branch names; the source does not state what access an attacker needs beyond that. Upgrade to Composer 2.2.24 for the 2.2 LTS line or 2.7.7 for the mainline line. Until then, the source suggests avoiding git installs by using --prefer-dist or the preferred-install: dist setting.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.8 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.011, the 64th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 10 Jun 2024, 20:54 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 14:05 UTC First seen by agentprime
  3. 31 Oct 2026, 14:05 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.