Forgejo 11.0 · Version Status
Forgejo 11.0 End of Life Date
Forgejo 11.0 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Forgejo 11.0 is past end of life. This version no longer receives security patches. 29 days past EOL — migrate to a supported version immediately.
EOL Date
Jul 16, 2026
29 days past EOL
Latest Release
11.0.16
LTS release
Release Date
Apr 16, 2025
Forgejo 11.0 series
Lifecycle detail
Forgejo 11.0 was released on April 16, 2025 and support ended on July 16, 2026 — a supported lifespan of 1 year and 3 months, in line with the 1 year and 3 months median for Forgejo LTS releases. It was a long-term support (LTS) release, so it received a longer patch window than the interim releases around it. The last patch it will ever receive is 11.0.16, published July 9, 2026 — 7 days before support ended. It has been without security patches for 29 days.
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 Forgejo 11.0 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 7.0 LTS |
7.0.16 |
Jul 17, 2025 |
EOL |
| 8.0 |
8.0.3 |
Oct 16, 2024 |
EOL |
| 9.0 |
9.0.3 |
Jan 16, 2025 |
EOL |
| 10.0 |
10.0.3 |
Apr 16, 2025 |
EOL |
| → 11.0 LTS |
11.0.16 |
Jul 16, 2026 |
EOL |
| 12.0 |
12.0.4 |
Oct 16, 2025 |
EOL |
| 13.0 |
13.0.5 |
Jan 29, 2026 |
EOL |
| 14.0 |
14.0.5 |
Apr 30, 2026 |
EOL |
What does Forgejo 11.0 end of life mean?
When Forgejo 11.0 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 Forgejo 11.0 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Forgejo 15.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Forgejo 11.0 reach end of life?
Forgejo 11.0 reached end of life on July 16, 2026. This version is no longer receiving security patches.
Is Forgejo 11.0 still supported?
No. Forgejo 11.0 reached end of life on July 16, 2026 and is no longer receiving security patches.
What should I upgrade to from Forgejo 11.0?
The recommended upgrade from Forgejo 11.0 is
Forgejo 15.0 — the latest actively supported version. Check the
Forgejo full timeline for all supported versions.
What are the security risks of running Forgejo 11.0 past EOL?
When Forgejo 11.0 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 Forgejo should migrate immediately or implement compensating controls.