Microsoft Office 2016 · Version Status
Microsoft Office 2016 End of Life Date
Microsoft Office 2016 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
Microsoft Office 2016 is past end of life. This version no longer receives security patches. 389 days past EOL — migrate to a supported version immediately.
EOL Date
Oct 14, 2025
389 days past EOL
Latest Release
—
Standard release
Release Date
Sep 22, 2015
Microsoft Office 2016 series
Where these dates come from
End of lifeOct 14, 2025Vendor's own page, read by our adapter · learn.microsoft.com · checked Nov 3, 2026high · 2 sources agree End of active supportOct 13, 2020Vendor's own page, read by our adapter · learn.microsoft.com · checked Nov 3, 2026high · 2 sources agree ReleaseSep 22, 2015Vendor's own page, read by our adapter · learn.microsoft.com · checked Nov 3, 2026high · 2 sources agree Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Microsoft Office 2016 was released on September 22, 2015 and support ended on October 14, 2025 — a supported lifespan of 10 years and 1 month, longer than the 7 years and 1 month median for Microsoft Office releases. It was not an LTS release; Microsoft Office reserves longer patch windows for its LTS releases. It has been past its end-of-life date for 1 year and 1 month.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended Microsoft Office 2016 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
All Microsoft Office Versions
What does Microsoft Office 2016 end of life mean?
When Microsoft Office 2016 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 Microsoft Office 2016 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Microsoft Office 2024 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Microsoft Office 2016 reach end of life?
Microsoft Office 2016 reached end of life on October 14, 2025. This version is no longer receiving security patches.
Is Microsoft Office 2016 still supported?
No. Microsoft Office 2016 reached end of life on October 14, 2025 and is no longer receiving security patches.
What should I upgrade to from Microsoft Office 2016?
The recommended upgrade from Microsoft Office 2016 is
Microsoft Office 2024 — the latest actively supported version. Check the
Microsoft Office full timeline for all supported versions.
What are the security risks of running Microsoft Office 2016 past EOL?
Since Microsoft Office 2016 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Microsoft Office should migrate immediately or implement compensating controls.