Complete end-of-life dates, support windows, and security status for all Office versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2007 | — | Jan 27, 2007 | Oct 10, 2017 | 3133 days past EOL | EOL |
| 2008-for-mac | — | Jan 15, 2008 | Apr 9, 2013 | 4778 days past EOL | EOL |
| 2010 | — | Jul 15, 2010 | Oct 13, 2020 | 2034 days past EOL | EOL |
| 2011-for-mac | — | Dec 9, 2010 | Oct 10, 2017 | 3133 days past EOL | EOL |
| 2013 | — | Jan 9, 2013 | Apr 11, 2023 | 1124 days past EOL | EOL |
| 2016 | — | Sep 22, 2015 | Oct 14, 2025 | 207 days past EOL | EOL |
| 2019 | — | Sep 24, 2018 | Oct 14, 2025 | 207 days past EOL | EOL |
| 2021 | — | Oct 5, 2021 | Oct 13, 2026 | 157 days remaining | Warning |
| 2024-ltsc LTS | — | Sep 18, 2024 | Oct 9, 2029 | 1249 days remaining | Active |
| 2024 | — | Oct 1, 2024 | Oct 9, 2029 | 1249 days remaining | Active |
When a Office version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Office should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →