Discourse 3.5 · Version Status
Discourse 3.5 End of Life Date
Discourse 3.5 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Discourse 3.5 is past end of life. This version no longer receives security patches. 101 days past EOL — migrate to a supported version immediately.
EOL Date
Jan 28, 2026
101 days past EOL
Latest Release
3.5.4
LTS release
Release Date
Aug 19, 2025
Discourse 3.5 series
| 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.3 |
Sep 30, 2026 |
Warning |
| 2026.2 |
2026.2.2 |
Apr 30, 2026 |
EOL |
| 2026.3 |
2026.3.0 |
May 31, 2026 |
Warning |
What does Discourse 3.5 end of life mean?
When Discourse 3.5 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 3.5 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to a supported version or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Discourse 3.5 reach end of life?
Discourse 3.5 reached end of life on January 28, 2026. This version is no longer receiving security patches.
Is Discourse 3.5 still supported?
No. Discourse 3.5 reached end of life on January 28, 2026 and is no longer receiving security patches.
What should I upgrade to from Discourse 3.5?
What are the security risks of running Discourse 3.5 past EOL?
When Discourse 3.5 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Discourse should migrate immediately or implement compensating controls.