← 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-2019-7777 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7776 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7775 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7774 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7772 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7773 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7771 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7770 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7768 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7767 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7766 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7765 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7764 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7763 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7762 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7761 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7760 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7759 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7758 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7145 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7144 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7143 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7142 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7141 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7769 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-7140 | 22 May 2019 | 2019.010.20100 and earlier, 2019.010.20099 and earlier, 2017.011.30140 and earlier version, 2017.011.30138 and earlier version, 2015.006.30495 and earlier, and 2015.006.30493 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-2018-19725 | 5 Mar 2019 | 2019.010.20069 and earlier versions; 2017.011.30113 and earlier versions; and 2015.006.30464 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-2018-19728 | 28 Jan 2019 | 2019.008.20081 and earlier, 2019.008.20080 and earlier, 2019.008.20081 and earlier, 2017.011.30106 and earlier version, 2017.011.30105 and earlier version, 2015.006.30457 and earlier, and 2015.006.30456 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-2018-15979 | 29 Nov 2018 | 2019.008.20080 and earlier, 2017.011.30105 and earlier, and 2015.006.30456 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-2018-15968 | 12 Oct 2018 | 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-15966 | 12 Oct 2018 | 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-15956 | 12 Oct 2018 | 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-15955 | 12 Oct 2018 | 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-15954 | 12 Oct 2018 | 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-15953 | 12 Oct 2018 | 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-15952 | 12 Oct 2018 | 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-15951 | 12 Oct 2018 | 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-15950 | 12 Oct 2018 | 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-15949 | 12 Oct 2018 | 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-15948 | 12 Oct 2018 | 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-15947 | 12 Oct 2018 | 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-15946 | 12 Oct 2018 | 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-15945 | 12 Oct 2018 | 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-15944 | 12 Oct 2018 | 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-15943 | 12 Oct 2018 | 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-15942 | 12 Oct 2018 | 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-15941 | 12 Oct 2018 | 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-15940 | 12 Oct 2018 | 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-15939 | 12 Oct 2018 | 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 and earlier versions | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-15938 | 12 Oct 2018 | 2018.011.20063 and earlier, 2017.011.30102 and earlier, and 2015.006.30452 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.