Forgejo End of Life (EOL) Dates & Support Timeline
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.
⚡Forgejo 11.0 reaches end of life on July 16, 2026. Plan your migration now — 23 days remaining.
📅 Get reminded before Forgejo 11.0 reaches EOL on July 16, 2026 — alerts 90, 30 & 7 days out.
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 →
Release Cycle Timeline
■ EOL
■ Warning
■ Active
┊ Today
All Versions
Version
Latest Release
Release Date
EOL Date
Days
Status
7.0 LTS
7.0.16
Apr 23, 2024
Jul 17, 2025
341 days past EOL
EOL
8.0
8.0.3
Jul 30, 2024
Oct 16, 2024
615 days past EOL
EOL
9.0
9.0.3
Oct 16, 2024
Jan 16, 2025
523 days past EOL
EOL
10.0
10.0.3
Jan 16, 2025
Apr 16, 2025
433 days past EOL
EOL
11.0 LTS
11.0.15
Apr 16, 2025
Jul 16, 2026
23 days remaining
Warning
12.0
12.0.4
Jul 17, 2025
Oct 16, 2025
250 days past EOL
EOL
13.0
13.0.5
Oct 16, 2025
Jan 29, 2026
145 days past EOL
EOL
14.0
14.0.5
Jan 15, 2026
Apr 30, 2026
54 days past EOL
EOL
15.0 LTS
15.0.3
Apr 16, 2026
Jul 15, 2027
387 days remaining
Active
What does Forgejo end of life mean for your organization?
When a version of Forgejo 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Forgejo versions. This is a bridge, not a permanent solution — plan your migration in parallel.
endoflife.ai
Need Extended Support?
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
The next Forgejo version reaching EOL is 11.0 on July 16, 2026. See the full table above for all version EOL dates.
When is the Forgejo support end date?
The next Forgejo support end date is July 16, 2026, when version 11.0 reaches end of support. Each version has its own support end date — see the table above for every version's date.
What is the latest supported version of Forgejo?
The latest active version of Forgejo is 15.0.3. Always verify against the table above as support windows can change.
What happens when Forgejo reaches end of life?
When Forgejo reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Forgejo?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Forgejo versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.