Complete end-of-life dates, support windows, and security status for all Forgejo versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 7.0 LTS | 7.0.16 | Apr 23, 2024 | Jul 17, 2025 | 296 days past EOL | EOL |
| 8.0 | 8.0.3 | Jul 30, 2024 | Oct 16, 2024 | 570 days past EOL | EOL |
| 9.0 | 9.0.3 | Oct 16, 2024 | Jan 16, 2025 | 478 days past EOL | EOL |
| 10.0 | 10.0.3 | Jan 16, 2025 | Apr 16, 2025 | 388 days past EOL | EOL |
| 11.0 LTS | 11.0.13 | Apr 16, 2025 | Jul 16, 2026 | 68 days remaining | Warning |
| 12.0 | 12.0.4 | Jul 17, 2025 | Oct 16, 2025 | 205 days past EOL | EOL |
| 13.0 | 13.0.5 | Oct 16, 2025 | Jan 29, 2026 | 100 days past EOL | EOL |
| 14.0 | 14.0.5 | Jan 15, 2026 | Apr 30, 2026 | 9 days past EOL | EOL |
| 15.0 LTS | 15.0.1 | Apr 16, 2026 | Jul 15, 2027 | 432 days remaining | Active |
When a Forgejo version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Forgejo should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →