Forgejo 15.0 · Version Status

Forgejo 15.0 End of Life Date

Forgejo 15.0 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Forgejo 15.0 is actively supported. EOL date: July 15, 2027.
EOL Date
Jul 15, 2027
432 days remaining
Latest Release
15.0.1
LTS release
Release Date
Apr 16, 2026
Forgejo 15.0 series
← Forgejo 14.0 All Forgejo versions
All Forgejo Versions
VersionLatestEOL DateStatus
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.13 Jul 16, 2026 Warning
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 15.0 end of life mean?

When Forgejo 15.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 15.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 15.0 reach end of life?
Forgejo 15.0 reached end of life on July 15, 2027. That is 432 days remaining.
Is Forgejo 15.0 still supported?
Yes, Forgejo 15.0 is currently supported. The EOL date is July 15, 2027.
What should I upgrade to from Forgejo 15.0?
The recommended upgrade from Forgejo 15.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 15.0 past EOL?
When Forgejo 15.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.
Data from endoflife.date API · Generated at build time · How we source data →