Forgejo 17.0 · Version Status
Forgejo 17.0 End of Life Date
Forgejo 17.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 17.0 reaches end of life on January 28, 2027. Plan your migration now — 100 days remaining.
📅 Get reminded before Forgejo 17.0 reaches EOL on January 28, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Jan 28, 2027
100 days remaining
Latest Release
17.0.0
Standard release
Release Date
Oct 15, 2026
Forgejo 17.0 series
Where these dates come from
End of lifeJan 28, 2027endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseOct 15, 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 17.0 was released on October 15, 2026 and support is scheduled to end on January 28, 2027 — a planned supported lifespan of 4 months, in line with the 4 months median for Forgejo releases. It is not an LTS release; Forgejo reserves longer patch windows for its LTS versions. Its most recent patch is 17.0.0, published October 15, 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 →
Extended Support
Extended Forgejo 17.0 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. 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 17.0 end of life mean?
When Forgejo 17.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 17.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 17.0 reach end of life?
Forgejo 17.0 reaches end of life on January 28, 2027. That is 100 days remaining.
Is Forgejo 17.0 still supported?
Forgejo 17.0 is still supported but approaching end of life on January 28, 2027. Begin planning your migration now.
What should I upgrade to from Forgejo 17.0?
The recommended upgrade from Forgejo 17.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 17.0 past EOL?
When Forgejo 17.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.