← Search results
CVE-LINKED INVENTORY29 SECURITY RECORDS
Adobe
Magento
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 Magento. 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-2020-9691 | 29 Jul 2020 | 2.3.5-p1 and earlier, and 2.3.5-p1 and earlier versions | 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-2020-9692 | 29 Jul 2020 | 2.3.5-p1 and earlier, and 2.3.5-p1 and earlier versions | 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-2020-9690 | 29 Jul 2020 | 2.3.5-p1 and earlier, and 2.3.5-p1 and earlier versions | 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-2020-9689 | 29 Jul 2020 | 2.3.5-p1 and earlier, and 2.3.5-p1 and earlier versions | 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-2020-9664 | 22 Jul 2020 | 1.14.4.5 and earlier, and 1.9.4.5 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-9665 | 22 Jul 2020 | 1.14.4.5 and earlier, and 1.9.4.5 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-9577 | 26 Jun 2020 | 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-9576 | 26 Jun 2020 | 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-9588 | 26 Jun 2020 | 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-9578 | 26 Jun 2020 | 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-9631 | 26 Jun 2020 | 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-9630 | 26 Jun 2020 | 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-9591 | 26 Jun 2020 | 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-9632 | 26 Jun 2020 | 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-9580 | 26 Jun 2020 | 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-9581 | 26 Jun 2020 | 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-9582 | 26 Jun 2020 | 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-9583 | 26 Jun 2020 | 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-9587 | 26 Jun 2020 | 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-9584 | 26 Jun 2020 | 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-9579 | 26 Jun 2020 | 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-9585 | 26 Jun 2020 | 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-3758 | 29 Jan 2020 | 2.3.3 and earlier; 2.2.10 and earlier; 1.14.4.3 and earlier; 1.9.4.3 and earlier versions | 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-2020-3719 | 29 Jan 2020 | 2.3.3 and earlier; 2.2.10 and earlier; 1.14.4.3 and earlier; 1.9.4.3 and earlier versions | 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-2020-3718 | 29 Jan 2020 | 2.3.3 and earlier; 2.2.10 and earlier; 1.14.4.3 and earlier; 1.9.4.3 and earlier versions | 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-2020-3717 | 29 Jan 2020 | 2.3.3 and earlier; 2.2.10 and earlier; 1.14.4.3 and earlier; 1.9.4.3 and earlier versions | 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-2020-3716 | 29 Jan 2020 | 2.3.3 and earlier; 2.2.10 and earlier; 1.14.4.3 and earlier; 1.9.4.3 and earlier versions | 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-2020-3715 | 29 Jan 2020 | 2.3.3 and earlier; 2.2.10 and earlier; 1.14.4.3 and earlier; 1.9.4.3 and earlier versions | 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-2019-8235 | 29 Oct 2019 | 2.3 prior to 2.3.1; 2.2 prior to 2.2.8; 2.1 prior to 2.1.17 | 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.