Advisory record · GHSA-gjfg-22fp-rrxx

Composer: Path traversal in package bin field lets dependencies chmod arbitrary host files

CVSS 6.1 MediumEPSS 0.0014 · 3rd percentile

Published by the GitHub Advisory Database at 20 Jul 2026, 21:57 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
composer/composerPackagist>=2.3.0, <2.10.2 || >=1.0.0, <2.2.292.10.2, 2.2.29
Identifiers
GHSA-gjfg-22fp-rrxx · BIT-composer-2026-59946 · CVE-2026-59946 · PKSA-q3ht-3g42-rg8f
Weakness (CWE)
CWE-22 · CWE-732
Published
20 Jul 2026
Updated
20 Jul 2026

Machine-written summary

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

Composer versions >=1.0.0 before 2.2.29, and 2.3.0 before 2.10.2, are vulnerable. A malicious or compromised package dependency, including a transitive one, can declare a bin entry with ".." path segments so that Composer changes the file mode of an existing file outside the package directory during install or update. The attacker can make restricted files, such as private keys, world-readable, but cannot read or modify their contents. Upgrade to Composer 2.2.29 or 2.10.2; no configuration workaround is given.

Written 3 Nov 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
6.1 Medium 3.1 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0014, the 3rd percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 1 Jul 2026, 09:31 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 14:25 UTC First seen by agentprime
  3. 31 Oct 2026, 14:25 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.