Composer 2.11.2, released on November 10, 2026, fixes a flaw that let a modified composer.lock run an arbitrary command on the machine. No malicious package has to be installed and no package script has to run: the command executes while Composer resolves downloads, before any checksum check. Version 2.2.32 shipped the same day for the 2.2 line, with part of the fixes.
Four advisories, one of them serious
Advisory GHSA-jhfp-4ppm-crmm is rated CVSS 8.8 (high). It affects versions 2.10.0 through 2.11.1. The prevent_url_access_callable transport option could be read from composer.lock or vendor/composer/installed.json, and a crafted value in those files made composer install or composer update call a system command. The advisory says --no-scripts and --no-plugins do not stop it. The 2.2 line and versions before 2.10 never had this option handling and are not affected.
The project's other two advisories are less severe but cover more versions:
- GHSA-x82q-x274-r6pq, CVSS 6.5: a modified lock file could name a download mirror controlled by someone else, and Composer sent it the HTTP credential configured for the private repository (a header token, for example). Affects 2.11.0, 2.11.1 and 2.2.31.
- GHSA-w6hj-6587-3jh5, CVSS 8.8: a package zip with symbolic links could write files outside the package folder, including overwriting the application's entry file. Affects 2.3.0 through 2.11.1 and every version before 2.2.32. The advisory itself says archives served by Packagist.org generally lack the required entries; the real risk lies in private repositories, artifact mirrors and download URLs outside Packagist.
The fourth item is an update to the bundled symfony/filesystem, which had its own flaw. The 2.11.2 notes also list three security changes without a formal advisory: Authorization and Cookie headers are no longer resent on redirects to another domain, non-auth settings are now ignored in auth.json and COMPOSER_AUTH, and blocked IP addresses are rejected before the request goes out.
The risk sits in the CI pipeline
Someone who runs Composer only on their own machine, with a lock file their own team generated, has little exposure to the main flaw. The advisory calls a different case the most realistic: a CI pipeline that checks out a branch and runs composer install without anyone reviewing the lock file change. A pull request that only touches composer.lock gets through review easily, because the file is long and almost nobody reads its diff. The advisory also mentions shared project templates, compromised dependency-update bots and poisoned CI caches.
This matters most for PHP projects open to outside contributions, for agencies that maintain many sites from a shared template, and for pipelines that keep deploy secrets in the same job that installs dependencies. In those cases, running a command on the runner amounts to access to everything the runner can see.
Update Composer everywhere it runs
The three advisories say the only complete fix is upgrading. For the main line, composer self-update takes you to 2.11.2; anyone still on the 2.2 line needs 2.2.32.
The larger job is finding every copy. Composer is often pinned in build Docker images, server provisioning scripts, CI actions that install a specific version, and the binary on each developer's machine. Updating the production server does not protect the pipeline, which is where a pull request's lock file gets executed.
Until every copy is on 2.11.2, the advisory's guidance is not to run composer install or composer update on lock or installed.json files from untrusted sources: unreviewed pull requests, third-party templates and shared caches. In practice, that means reviewing the rule that triggers the install job for outside contributions.
What is still unknown
None of the advisories has a CVE assigned so far, and audit tools that only match CVEs may not flag the vulnerable version. The project also does not say whether the flaw was exploited before the fix. And the notes do not say when managed PHP platforms and official CI images will ship the fixed version by default; anyone relying on them should check the installed version rather than assume it was updated.
If your company is weighing something similar, reach me on LinkedIn or WhatsApp.