← Search results
CVE-LINKED INVENTORY16 SECURITY RECORDS
composer
composer
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at composer, but registry activity is not a publisher support boundary.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-59944 | 16 Sep 2026 | composer: >= 1.0.0, < 2.2.30, >= 2.3.0, < 2.10.3 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ | Update reference ↗ |
| CVE-2026-84361 | 1 Sep 2026 | >= 1.0, < 2.2.30; >= 2.3.0, < 2.10.3 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ | Update reference ↗ |
| CVE-2026-45793 | 15 Jul 2026 | >= 1.0, < 1.10.28; >= 2.0.0, < 2.2.28; >= 2.3.0, < 2.9.8 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-59947 | 8 Jul 2026 | >= 1.0, < 2.2.29; >= 2.3.0, < 2.10.2 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-59948 | 8 Jul 2026 | >= 1.0, < 2.2.29; >= 2.3.0, < 2.10.2 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-59946 | 8 Jul 2026 | >= 1.0, < 2.2.29; >= 2.3.0, < 2.10.2 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-40261 | 15 Apr 2026 | >= 2.3.0, < 2.9.6; >= 1.0.0, < 2.2.27 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-40176 | 15 Apr 2026 | >= 2.3, < 2.9.6; >= 1.0, < 2.2.27 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-67746 | 30 Dec 2025 | >= 2.0, < 2.2.26; >= 2.3, < 2.9.3 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-35242 | 10 Jun 2024 | >= 2.0, < 2.2.24; >= 2.3, < 2.7.7 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-35241 | 10 Jun 2024 | >= 2.0, < 2.2.24; >= 2.3, < 2.7.7 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-24821 | 8 Feb 2024 | >= 2.0, < 2.2.23; >= 2.3, < 2.7 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-43655 | 29 Sep 2023 | 2.6.4, 2.2.21, 1.10.27; >= 2.0, < 2.2.22; < 1.10.27 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-24828 | 13 Apr 2022 | < 1.10.26; >= 2.0.0, < 2.2.12; >= 2.3, < 2.3.6 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-41116 | 5 Oct 2021 | < 1.10.23; >= 2.0, < 2.1.9 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-29472 | 27 Apr 2021 | < 1.10.22; >=2.0,<2.0.13 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.