CISA list

Composer versions

Composer: update to 2.11.2 or 2.2.32. 2.10, 2.9, 2.8, 2.7, 2.6, 2.5, 2.4, 2.3 and 2.1 and older no longer get fixes.

Data: .

Which Composer branch to run

The newest safe release is the newest release of a branch that still gets fixes and that no CVE record we read names as affected. Records whose versions we cannot place on a branch are named at the end of the page.

Which Composer branch to run
BranchStatusNewest safe releaseUpgrade to
2.11Fixes, no end date announced2.11.22.11.2 (this branch)
2.105 CVE records that this page readsEnded on 29 October 2026None, the branch has ended2.11.2 (move to 2.11)
2.94 CVE records that this page readsEnded on 28 May 2026None, the branch has ended2.11.2 (move to 2.11)
2.8Ended on 13 November 2025None, the branch has ended2.11.2 (move to 2.11)
2.72 CVE records that this page readsEnded on 2 October 2024None, the branch has ended2.11.2 (move to 2.11)
2.6Ended on 8 February 2024None, the branch has ended2.11.2 (move to 2.11)
2.5Ended on 1 September 2023None, the branch has ended2.11.2 (move to 2.11)
2.4Ended on 20 December 2022None, the branch has ended2.11.2 (move to 2.11)
2.31 CVE record that this page readsEnded on 16 August 2022None, the branch has ended2.11.2 (move to 2.11)
2.212 CVE records that this page readsFixes until 31 December 20262.2.322.2.32 (this branch)
2.11 CVE record that this page readsEnded on 22 December 2021None, the branch has ended2.2.32 (move to 2.2)
2.01 CVE record that this page readsEnded on 3 June 2021None, the branch has ended2.2.32 (move to 2.2)
14 CVE records that this page readsEnded on 30 May 2026None, the branch has ended2.2.32 (move to 2.2)

What this page counts

The branches, their dates and the newest release of each are from the product lifecycle data credited under Sources. A later release that a CVE record names as a fix counts as the newest too.

This page reads 16 CVE records that the CVE Numbering Authority GitHub_M (as the CVE List names it) published and that name Composer. The fixes are from the 14 it places on a branch. A record says a release fixes a flaw when its affected range for a branch ends before that release. A record from any other source gives no version here.

No release of a branch that has ended is called safe here.

Some records give a range with no start: from 0, or before a release. A record is placed on the branch of the release that ends its range. As the record states it, the range also covers every older release. Such a range is not counted when the newest safe release of a branch that still gets fixes is worked out.

Some records give a range that starts in an older branch and ends in a newer one. A record is placed on the branch of the release that ends its range, and as the record states it, the range also covers the older branches it runs across. Only a range that runs across branches that have all ended is placed: a range that reaches a branch that still gets fixes would name that branch's newest release as affected, which a project that also fixes its older branches does not mean. Such a record is named at the end of the page.

2 records are not placed on a branch, so no branch or release row counts them: CVE-2023-43655 and CVE-2024-24821.

Sources
  • CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
  • Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
  • EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)