Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY65 SECURITY RECORDS

Adobe Systems Incorporated

Acrobat Reader

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

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

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2017-11226 11 Aug 2017 2017.009.20058 and earlier; 2017.008.30051 and earlier; 2015.006.30306 and earlier; 11.0.20 and earlier 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-2017-11224 11 Aug 2017 2017.009.20058 and earlier; 2017.008.30051 and earlier; 2015.006.30306 and earlier; 11.0.20 and earlier 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-2017-11223 11 Aug 2017 2017.009.20058 and earlier; 2017.008.30051 and earlier; 2015.006.30306 and earlier; 11.0.20 and earlier 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-2017-11222 11 Aug 2017 2017.009.20058 and earlier; 2017.008.30051 and earlier; 2015.006.30306 and earlier; 11.0.20 and earlier 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-2017-11221 11 Aug 2017 2017.009.20058 and earlier; 2017.008.30051 and earlier; 2015.006.30306 and earlier; 11.0.20 and earlier 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-2017-11220 11 Aug 2017 2017.009.20058 and earlier; 2017.008.30051 and earlier; 2015.006.30306 and earlier; 11.0.20 and earlier 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-2017-11219 11 Aug 2017 2017.009.20058 and earlier; 2017.008.30051 and earlier; 2015.006.30306 and earlier; 11.0.20 and earlier 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-2017-11218 11 Aug 2017 2017.009.20058 and earlier; 2017.008.30051 and earlier; 2015.006.30306 and earlier; 11.0.20 and earlier 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-2017-11217 11 Aug 2017 2017.009.20058 and earlier; 2017.008.30051 and earlier; 2015.006.30306 and earlier; 11.0.20 and earlier 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-2017-11216 11 Aug 2017 2017.009.20058 and earlier; 2017.008.30051 and earlier; 2015.006.30306 and earlier; 11.0.20 and earlier 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-2017-11214 11 Aug 2017 2017.009.20058 and earlier; 2017.008.30051 and earlier; 2015.006.30306 and earlier; 11.0.20 and earlier 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-2017-11212 11 Aug 2017 2017.009.20058 and earlier; 2017.008.30051 and earlier; 2015.006.30306 and earlier; 11.0.20 and earlier 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-2017-11211 11 Aug 2017 2017.009.20058 and earlier; 2017.008.30051 and earlier; 2015.006.30306 and earlier; 11.0.20 and earlier 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-2017-11210 11 Aug 2017 2017.009.20058 and earlier; 2017.008.30051 and earlier; 2015.006.30306 and earlier; 11.0.20 and earlier 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-2017-11209 11 Aug 2017 2017.009.20058 and earlier; 2017.008.30051 and earlier; 2015.006.30306 and earlier; 11.0.20 and earlier 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.