Discourse 2025.12 End of Life Date
Discourse 2025.12 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.
Discourse 2025.12 was released on December 30, 2025 and support ended on February 26, 2026 — a supported lifespan of 2 months, in line with the 2 months median for Discourse releases. It was not an LTS release; Discourse reserves longer patch windows for its LTS versions. The last patch it will ever receive is 2025.12.2, published February 26, 2026 — on the day support ended. It has been without security patches for 7 months. 6 newer Discourse releases have shipped since.
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →| Version | Latest | EOL Date | Status |
|---|---|---|---|
| 3.4 LTS | 3.4.7 | Aug 19, 2025 | EOL |
| 3.5 LTS | 3.5.4 | Jan 28, 2026 | EOL |
| 2025.11 | 2025.11.2 | Jan 28, 2026 | EOL |
| → 2025.12 | 2025.12.2 | Feb 26, 2026 | EOL |
| 2026.1 LTS | 2026.1.8 | Sep 30, 2026 | Warning |
| 2026.2 | 2026.2.2 | Apr 28, 2026 | EOL |
| 2026.3 | 2026.3.1 | May 28, 2026 | EOL |
| 2026.4 | 2026.4.2 | Jun 30, 2026 | EOL |
What does Discourse 2025.12 end of life mean?
When Discourse 2025.12 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 Discourse 2025.12 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Discourse 2026.7 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.