Gitea 1.26 · Version Status
Gitea 1.26 End of Life Date
Gitea 1.26 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Gitea 1.26 is past end of life. This version no longer receives security patches. 44 days past EOL — migrate to a supported version immediately.
EOL Date
Jul 13, 2026
44 days past EOL
Latest Release
1.26.4
Standard release
Release Date
Apr 18, 2026
Gitea 1.26 series
Lifecycle detail
Gitea 1.26 was released on April 18, 2026 and support ended on July 13, 2026 — a supported lifespan of 3 months, shorter than the 5 months median for Gitea releases. The last patch it will ever receive is 1.26.4, published June 21, 2026 — 22 days before support ended. It has been without security patches for 44 days.
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 Gitea 1.26 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
| 1.17 |
1.17.4 |
Dec 29, 2022 |
EOL |
| 1.18 |
1.18.5 |
Mar 20, 2023 |
EOL |
| 1.19 |
1.19.4 |
Jul 16, 2023 |
EOL |
| 1.20 |
1.20.6 |
Nov 14, 2023 |
EOL |
| 1.21 |
1.21.11 |
May 27, 2024 |
EOL |
| 1.22 |
1.22.6 |
Jan 9, 2025 |
EOL |
| 1.23 |
1.23.8 |
Jun 10, 2025 |
EOL |
| 1.24 |
1.24.7 |
Oct 29, 2025 |
EOL |
What does Gitea 1.26 end of life mean?
When Gitea 1.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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Gitea 1.26 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Gitea 1.27 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Gitea 1.26 reach end of life?
Gitea 1.26 reached end of life on July 13, 2026. This version is no longer receiving security patches.
Is Gitea 1.26 still supported?
No. Gitea 1.26 reached end of life on July 13, 2026 and is no longer receiving security patches.
What should I upgrade to from Gitea 1.26?
The recommended upgrade from Gitea 1.26 is
Gitea 1.27 — the latest actively supported version. Check the
Gitea full timeline for all supported versions.
What are the security risks of running Gitea 1.26 past EOL?
When Gitea 1.26 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Gitea should migrate immediately or implement compensating controls.