Complete end-of-life dates, support windows, and security status for all Discourse versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 3.4 LTS | 3.4.7 | Feb 4, 2025 | Aug 19, 2025 | 263 days past EOL | EOL |
| 3.5 LTS | 3.5.4 | Aug 19, 2025 | Jan 28, 2026 | 101 days past EOL | EOL |
| 2025.11 | 2025.11.2 | Nov 25, 2025 | Jan 28, 2026 | 101 days past EOL | EOL |
| 2025.12 | 2025.12.2 | Dec 30, 2025 | Feb 26, 2026 | 72 days past EOL | EOL |
| 2026.1 LTS | 2026.1.3 | Jan 28, 2026 | Sep 30, 2026 | 144 days remaining | Warning |
| 2026.2 | 2026.2.2 | Feb 26, 2026 | Apr 30, 2026 | 9 days past EOL | EOL |
| 2026.3 | 2026.3.0 | Mar 31, 2026 | May 31, 2026 | 22 days remaining | Warning |
When a Discourse 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 Discourse 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 →