← Search results
CVE-LINKED INVENTORY38 SECURITY RECORDS
Shopware
Shopware
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This CVE identity is linked to the Lifecycle record Shopware. Use that record for publisher support phases and retirement dates.
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-48012 | 23 Jul 2026 | >= 6.7.3.0, < 6.7.10.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-48013 | 23 Jul 2026 | < 6.6.10.18; >= 6.7.0.0, < 6.7.10.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-48009 | 17 Jul 2026 | < 6.6.10.18; >= 6.7.0.0, < 6.7.10.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-48014 | 17 Jul 2026 | < 6.6.10.18; >= 6.7.0.0, < 6.7.10.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-48010 | 17 Jul 2026 | < 6.6.10.18; >= 6.7.0.0, < 6.7.10.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-48016 | 17 Jul 2026 | < 6.6.10.18; >= 6.7.0.0, < 6.7.10.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-48015 | 17 Jul 2026 | < 6.6.10.18; >= 6.7.0.0, < 6.7.10.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-48008 | 17 Jul 2026 | < 6.6.10.18; >= 6.7.0.0, < 6.7.10.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-48011 | 10 Jun 2026 | >= 6.7.0.0, < 6.7.10.1; < 6.6.10.18 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-23498 | 14 Jan 2026 | >= 6.7.0.0, < 6.7.6.1 | 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-2025-67648 | 10 Dec 2025 | >= 6.4.6.0, < 6.6.10.10; >= 6.7.0.0, < 6.7.5.1 | 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-2025-7954 | 6 Aug 2025 | 6.6.x; 6.7.x | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-32378 | 9 Apr 2025 | < 6.5.8.17; >= 6.6.0.0, < 6.6.10.3; >= 6.7.0.0-rc1, < 6.7.0.0-rc2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-30150 | 8 Apr 2025 | < 6.5.8.17; >= 6.6.0.0, < 6.6.10.3; >= 6.7.0.0-rc1, < 6.7.0.0-rc2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-30151 | 8 Apr 2025 | < 6.5.8.17; >= 6.6.0.0, < 6.6.10.3; >= 6.7.0.0-rc1, < 6.7.0.0-rc2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-42357 | 8 Aug 2024 | >= 6.6.0.0, <= 6.6.5.0; <= 6.5.8.12 | 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-42356 | 8 Aug 2024 | <= 6.5.8.12; >= 6.6.0.0, <= 6.6.5.0 | 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-42355 | 8 Aug 2024 | <= 6.5.8.12; >= 6.6.0.0, <= 6.6.5.0 | 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-42354 | 8 Aug 2024 | <= 6.5.8.12; >= 6.6.0.0, <= 6.6.5.0 | 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-31447 | 8 Apr 2024 | >= 6.3.5.0, < 6.5.8.8; >= 6.6.0.0-rc1, < 6.6.1.0 | 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-27917 | 6 Mar 2024 | >= 6.5.8.0, < 6.5.8.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-2024-22406 | 16 Jan 2024 | < 6.5.7.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-22407 | 16 Jan 2024 | < 6.5.7.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-22408 | 16 Jan 2024 | < 6.5.7.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-34099 | 27 Jun 2023 | < 5.7.18 | 5.7.18 | Update reference ↗ |
| CVE-2023-34098 | 27 Jun 2023 | < 5.7.18 | 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-36102 | 12 Sep 2022 | < 5.7.15 | 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-36101 | 12 Sep 2022 | < 5.7.15 | 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-31148 | 1 Aug 2022 | >= 5.7.0, < 5.7.14 | 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-31057 | 27 Jun 2022 | < 5.7.12 | 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-24892 | 28 Apr 2022 | >= 5.0.4, < 5.7.9 | 5.7.9. | Update reference ↗ |
| CVE-2022-24879 | 28 Apr 2022 | >= 5.2.0, < 5.7.9 | 5.7.9. | Update reference ↗ |
| CVE-2022-24873 | 28 Apr 2022 | < 5.7.9 | 5.7.9. | Update reference ↗ |
| CVE-2022-21652 | 5 Jan 2022 | >=5.7.3, < 5.7.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-2022-21651 | 5 Jan 2022 | >= 5.0.0, < 5.7.7 | 5.7.7. | Update reference ↗ |
| CVE-2021-41188 | 26 Oct 2021 | < 5.7.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-32712 | 24 Jun 2021 | < 5.6.10 | 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-32713 | 24 Jun 2021 | < 5.6.10 | 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 ↗ |
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.