← Search results
CVE-LINKED INVENTORY515 SECURITY RECORDS
Adobe
Adobe Acrobat and Reader
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
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-9610 | 25 Jun 2020 | 2020.006.20042 and earlier, 2017.011.30166 and earlier, 2017.011.30166 and earlier, and 2015.006.30518 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-9612 | 25 Jun 2020 | 2020.006.20042 and earlier, 2017.011.30166 and earlier, 2017.011.30166 and earlier, and 2015.006.30518 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-9614 | 25 Jun 2020 | 2020.006.20042 and earlier, 2017.011.30166 and earlier, 2017.011.30166 and earlier, and 2015.006.30518 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-9592 | 25 Jun 2020 | 2020.006.20042 and earlier, 2017.011.30166 and earlier, 2017.011.30166 and earlier, and 2015.006.30518 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-3803 | 25 Mar 2020 | , 2020.006.20034 and earlier, 2017.011.30158 and earlier, 2017.011.30158 and earlier, 2015.006.30510 and earlier, and 2015.006.30510 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-3807 | 25 Mar 2020 | , 2020.006.20034 and earlier, 2017.011.30158 and earlier, 2017.011.30158 and earlier, 2015.006.30510 and earlier, and 2015.006.30510 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-3804 | 25 Mar 2020 | , 2020.006.20034 and earlier, 2017.011.30158 and earlier, 2017.011.30158 and earlier, 2015.006.30510 and earlier, and 2015.006.30510 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-3806 | 25 Mar 2020 | , 2020.006.20034 and earlier, 2017.011.30158 and earlier, 2017.011.30158 and earlier, 2015.006.30510 and earlier, and 2015.006.30510 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-3802 | 25 Mar 2020 | , 2020.006.20034 and earlier, 2017.011.30158 and earlier, 2017.011.30158 and earlier, 2015.006.30510 and earlier, and 2015.006.30510 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-3805 | 25 Mar 2020 | , 2020.006.20034 and earlier, 2017.011.30158 and earlier, 2017.011.30158 and earlier, 2015.006.30510 and earlier, and 2015.006.30510 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-3801 | 25 Mar 2020 | , 2020.006.20034 and earlier, 2017.011.30158 and earlier, 2017.011.30158 and earlier, 2015.006.30510 and earlier, and 2015.006.30510 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-3800 | 25 Mar 2020 | , 2020.006.20034 and earlier, 2017.011.30158 and earlier, 2017.011.30158 and earlier, 2015.006.30510 and earlier, and 2015.006.30510 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-3797 | 25 Mar 2020 | , 2020.006.20034 and earlier, 2017.011.30158 and earlier, 2017.011.30158 and earlier, 2015.006.30510 and earlier, and 2015.006.30510 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-3799 | 25 Mar 2020 | , 2020.006.20034 and earlier, 2017.011.30158 and earlier, 2017.011.30158 and earlier, 2015.006.30510 and earlier, and 2015.006.30510 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-3795 | 25 Mar 2020 | , 2020.006.20034 and earlier, 2017.011.30158 and earlier, 2017.011.30158 and earlier, 2015.006.30510 and earlier, and 2015.006.30510 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-3793 | 25 Mar 2020 | , 2020.006.20034 and earlier, 2017.011.30158 and earlier, 2017.011.30158 and earlier, 2015.006.30510 and earlier, and 2015.006.30510 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-3792 | 25 Mar 2020 | , 2020.006.20034 and earlier, 2017.011.30158 and earlier, 2017.011.30158 and earlier, 2015.006.30510 and earlier, and 2015.006.30510 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-3750 | 13 Feb 2020 | , 2019.021.20061 and earlier, 2017.011.30156 and earlier, 2017.011.30156 and earlier, and 2015.006.30508 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-3754 | 13 Feb 2020 | , 2019.021.20061 and earlier, 2017.011.30156 and earlier, 2017.011.30156 and earlier, and 2015.006.30508 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-3752 | 13 Feb 2020 | , 2019.021.20061 and earlier, 2017.011.30156 and earlier, 2017.011.30156 and earlier, and 2015.006.30508 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-3745 | 13 Feb 2020 | , 2019.021.20061 and earlier, 2017.011.30156 and earlier, 2017.011.30156 and earlier, and 2015.006.30508 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-3751 | 13 Feb 2020 | , 2019.021.20061 and earlier, 2017.011.30156 and earlier, 2017.011.30156 and earlier, and 2015.006.30508 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-3755 | 13 Feb 2020 | , 2019.021.20061 and earlier, 2017.011.30156 and earlier, 2017.011.30156 and earlier, and 2015.006.30508 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-3753 | 13 Feb 2020 | , 2019.021.20061 and earlier, 2017.011.30156 and earlier, 2017.011.30156 and earlier, and 2015.006.30508 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-3749 | 13 Feb 2020 | , 2019.021.20061 and earlier, 2017.011.30156 and earlier, 2017.011.30156 and earlier, and 2015.006.30508 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-3744 | 13 Feb 2020 | , 2019.021.20061 and earlier, 2017.011.30156 and earlier, 2017.011.30156 and earlier, and 2015.006.30508 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-3747 | 13 Feb 2020 | , 2019.021.20061 and earlier, 2017.011.30156 and earlier, 2017.011.30156 and earlier, and 2015.006.30508 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-3746 | 13 Feb 2020 | , 2019.021.20061 and earlier, 2017.011.30156 and earlier, 2017.011.30156 and earlier, and 2015.006.30508 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-3743 | 13 Feb 2020 | , 2019.021.20061 and earlier, 2017.011.30156 and earlier, 2017.011.30156 and earlier, and 2015.006.30508 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-3762 | 13 Feb 2020 | , 2019.021.20061 and earlier, 2017.011.30156 and earlier, 2017.011.30156 and earlier, and 2015.006.30508 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-3756 | 13 Feb 2020 | , 2019.021.20061 and earlier, 2017.011.30156 and earlier, 2017.011.30156 and earlier, and 2015.006.30508 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-3763 | 13 Feb 2020 | , 2019.021.20061 and earlier, 2017.011.30156 and earlier, 2017.011.30156 and earlier, and 2015.006.30508 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-3748 | 13 Feb 2020 | , 2019.021.20061 and earlier, 2017.011.30156 and earlier, 2017.011.30156 and earlier, and 2015.006.30508 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-3742 | 13 Feb 2020 | , 2019.021.20061 and earlier, 2017.011.30156 and earlier, 2017.011.30156 and earlier, and 2015.006.30508 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-7131 | 27 Jan 2020 | 2019.010.20064 and earlier, 2019.010.20064 and earlier, 2017.011.30110 and earlier version, and 2015.006.30461 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-8257 | 27 Jan 2020 | 2019.012.20035 and earlier, 2019.012.20035 and earlier, 2017.011.30142 and earlier, 2017.011.30143 and earlier, 2015.006.30497 and earlier, and 2015.006.30498 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-16465 | 19 Dec 2019 | , 2019.021.20056 and earlier, 2017.011.30152 and earlier, 2017.011.30155 and earlier version, 2017.011.30152 and earlier, and 2015.006.30505 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-16464 | 19 Dec 2019 | , 2019.021.20056 and earlier, 2017.011.30152 and earlier, 2017.011.30155 and earlier version, 2017.011.30152 and earlier, and 2015.006.30505 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-16463 | 19 Dec 2019 | , 2019.021.20056 and earlier, 2017.011.30152 and earlier, 2017.011.30155 and earlier version, 2017.011.30152 and earlier, and 2015.006.30505 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-16462 | 19 Dec 2019 | , 2019.021.20056 and earlier, 2017.011.30152 and earlier, 2017.011.30155 and earlier version, 2017.011.30152 and earlier, and 2015.006.30505 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-16461 | 19 Dec 2019 | , 2019.021.20056 and earlier, 2017.011.30152 and earlier, 2017.011.30155 and earlier version, 2017.011.30152 and earlier, and 2015.006.30505 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-16460 | 19 Dec 2019 | , 2019.021.20056 and earlier, 2017.011.30152 and earlier, 2017.011.30155 and earlier version, 2017.011.30152 and earlier, and 2015.006.30505 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-16459 | 19 Dec 2019 | , 2019.021.20056 and earlier, 2017.011.30152 and earlier, 2017.011.30155 and earlier version, 2017.011.30152 and earlier, and 2015.006.30505 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-16458 | 19 Dec 2019 | , 2019.021.20056 and earlier, 2017.011.30152 and earlier, 2017.011.30155 and earlier version, 2017.011.30152 and earlier, and 2015.006.30505 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-16457 | 19 Dec 2019 | , 2019.021.20056 and earlier, 2017.011.30152 and earlier, 2017.011.30155 and earlier version, 2017.011.30152 and earlier, and 2015.006.30505 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-16456 | 19 Dec 2019 | , 2019.021.20056 and earlier, 2017.011.30152 and earlier, 2017.011.30155 and earlier version, 2017.011.30152 and earlier, and 2015.006.30505 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-16455 | 19 Dec 2019 | , 2019.021.20056 and earlier, 2017.011.30152 and earlier, 2017.011.30155 and earlier version, 2017.011.30152 and earlier, and 2015.006.30505 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-16454 | 19 Dec 2019 | , 2019.021.20056 and earlier, 2017.011.30152 and earlier, 2017.011.30155 and earlier version, 2017.011.30152 and earlier, and 2015.006.30505 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-16453 | 19 Dec 2019 | , 2019.021.20056 and earlier, 2017.011.30152 and earlier, 2017.011.30155 and earlier version, 2017.011.30152 and earlier, and 2015.006.30505 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-16452 | 19 Dec 2019 | , 2019.021.20056 and earlier, 2017.011.30152 and earlier, 2017.011.30155 and earlier version, 2017.011.30152 and earlier, and 2015.006.30505 and earlier versions | 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.