Nextcloud 26 · Version Status
Nextcloud 26 End of Life Date
Nextcloud 26 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.
⚠
Nextcloud 26 is past end of life. This version no longer receives security patches. 951 days past EOL — migrate to a supported version immediately.
EOL Date
Mar 31, 2024
951 days past EOL
Latest Release
26.0.13
Standard release
Release Date
Mar 21, 2023
Nextcloud 26 series
Where these dates come from
End of lifeMar 31, 2024endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseMar 21, 2023endoflife.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
Nextcloud 26 was released on March 21, 2023 and support ended on March 31, 2024 — a supported lifespan of 1 year, in line with the 1 year and 1 month median for Nextcloud releases. Its latest release on record is 26.0.13, published March 28, 2024 — 3 days before support ended. It has been past its end-of-life date for 2 years and 7 months. 7 newer Nextcloud releases have 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 Nextcloud 26 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 |
|---|
| 9 |
9.1.3 |
Aug 31, 2017 |
EOL |
| 10 |
10.0.6 |
Aug 31, 2017 |
EOL |
| 11 |
11.0.8 |
Mar 31, 2018 |
EOL |
| 12 |
12.0.13 |
Nov 30, 2018 |
EOL |
| 13 |
13.0.12 |
Feb 28, 2019 |
EOL |
| 14 |
14.0.14 |
Sep 30, 2019 |
EOL |
| 15 |
15.0.14 |
Dec 31, 2019 |
EOL |
| 16 |
16.0.11 |
Jun 30, 2020 |
EOL |
What does Nextcloud 26 end of life mean?
When Nextcloud 26 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 Nextcloud 26 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Nextcloud 35 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Nextcloud 26 reach end of life?
Nextcloud 26 reached end of life on March 31, 2024. This version is no longer receiving security patches.
Is Nextcloud 26 still supported?
No. Nextcloud 26 reached end of life on March 31, 2024 and is no longer receiving security patches.
What should I upgrade to from Nextcloud 26?
The recommended upgrade from Nextcloud 26 is
Nextcloud 35 — the latest actively supported version. Check the
Nextcloud full timeline for all supported versions.
What are the security risks of running Nextcloud 26 past EOL?
Since Nextcloud 26 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 Nextcloud should migrate immediately or implement compensating controls.