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 reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
✓
Forgejo 15.0 is actively supported. EOL date: July 15, 2027.
📅 Get reminded before Forgejo 15.0 reaches EOL on July 15, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Jul 15, 2027
250 days remaining
Latest Release
15.0.11
LTS release
Release Date
Apr 16, 2026
Forgejo 15.0 series
Where these dates come from
End of lifeJul 15, 2027endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseApr 16, 2026endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees
Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Forgejo 15.0 was released on April 16, 2026 and support is scheduled to end on July 15, 2027 — a planned supported lifespan of 1 year and 3 months, in line with the 1 year and 3 months median for Forgejo LTS releases. It is a long-term support (LTS) release, so it carries a longer patch window than the interim releases around it. Its most recent patch is 15.0.11, published October 26, 2026.
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 →
| 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 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Forgejo 15.0 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
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 reaches end of life on July 15, 2027. That is 250 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 vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Forgejo should migrate immediately or implement compensating controls.