Adobe Acrobat Continuous track (Acrobat and Acrobat Reader) End of Life Date
Adobe Acrobat Continuous track (Acrobat and Acrobat Reader) end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (helpx.adobe.com); the source of each date is on the product page.
| Version | Latest | EOL Date | Status |
|---|---|---|---|
| Acrobat 7 / Reader 7 | 7 | Dec 28, 2009 | EOL |
| Acrobat 8 / Reader 8 | 8 | Nov 3, 2011 | EOL |
| Acrobat 9 / Reader 9 | 9 | Jun 26, 2013 | EOL |
| Acrobat X / Reader X | 10 | Nov 15, 2015 | EOL |
| Acrobat XI / Reader XI | 11 | Oct 15, 2017 | EOL |
| Acrobat 2015 (Classic track, Acrobat DC) | 2015 | Jul 7, 2020 | EOL |
| Acrobat 2017 (Classic track) | 2017 | Jun 6, 2022 | EOL |
| Acrobat 2020 (Classic track) | 2020 | Nov 30, 2025 | EOL |
What does Adobe Acrobat Continuous track (Acrobat and Acrobat Reader) end of life mean?
When Adobe Acrobat Continuous track (Acrobat and Acrobat Reader) reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Adobe Acrobat Continuous track (Acrobat and Acrobat Reader) past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Adobe Acrobat Acrobat 2024 (Classic track) or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.