Generated remediation guidance and an executive summary. No account required.
Composer 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 of the way that dist packages are cached. The cache key is derived from the package name, the dist type, and certain other data from the package repository (which may simply be a commit hash, and thus can be found by an attacker). Versions through 1.0.0-alpha11 are affected, and 1.0.0 is unaffected.
Cite this page
CVE-2015-8371. CVEDatabase.com. Retrieved 1 May 2026. https://cvedatabase.com/cve/CVE-2015-8371
Use CWE-345, Getcomposer vendor hub and Composer product page to widen CVE-2015-8371 into its surrounding weakness, vendor, and product context.
Compare it with CVE-2026-40261, CVE-2024-24821 and CVE-2021-29472 for nearby disclosures in the same product family.