Umbraco 16 · Version Status
Umbraco 16 End of Life Date
Umbraco 16 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.
⚠
Umbraco 16 is past end of life. This version no longer receives security patches. 148 days past EOL — migrate to a supported version immediately.
EOL Date
Jun 12, 2026
148 days past EOL
Latest Release
16.5.1
Standard release
Release Date
Jun 12, 2025
Umbraco 16 series
Where these dates come from
End of lifeJun 12, 2026endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees End of active supportMar 12, 2026endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseJun 12, 2025endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees 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
Umbraco 16 was released on June 12, 2025 and support ended on June 12, 2026 — a supported lifespan of 1 year, shorter than the 1 year and 3 months median for Umbraco releases. It was not an LTS release; Umbraco reserves longer patch windows for its LTS releases. Its latest release on record is 16.5.1, published March 10, 2026 — 3 months before support ended. It has been past its end-of-life date for 5 months. 1 newer Umbraco release has shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in 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 Umbraco 16 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 →
| Version | Latest | EOL Date | Status |
|---|
| 6 |
6.2.6 |
May 1, 2018 |
EOL |
| 7 LTS |
7.15.11 |
Sep 30, 2023 |
EOL |
| 8 LTS |
8.18.15 |
Feb 24, 2025 |
EOL |
| 9 |
9.5.4 |
Dec 16, 2022 |
EOL |
| 10 LTS |
10.8.11 |
Jun 16, 2025 |
EOL |
| 11 |
11.5.0 |
Dec 1, 2023 |
EOL |
| 12 |
12.3.10 |
Jun 29, 2024 |
EOL |
| 13 LTS |
13.16.4 |
Dec 14, 2026 |
Warning |
What does Umbraco 16 end of life mean?
When Umbraco 16 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 Umbraco 16 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Umbraco 18 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Umbraco 16 reach end of life?
Umbraco 16 reached end of life on June 12, 2026. This version is no longer receiving security patches.
Is Umbraco 16 still supported?
No. Umbraco 16 reached end of life on June 12, 2026 and is no longer receiving security patches.
What should I upgrade to from Umbraco 16?
The recommended upgrade from Umbraco 16 is
Umbraco 18 — the latest actively supported version. Check the
Umbraco full timeline for all supported versions.
What are the security risks of running Umbraco 16 past EOL?
Since Umbraco 16 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 Umbraco should migrate immediately or implement compensating controls.