Discourse 2026.10 · Version Status
Discourse 2026.10 End of Life Date
Discourse 2026.10 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 2026.10 reaches end of life on December 29, 2026. Plan your migration now — 60 days remaining.
📅 Get reminded before Discourse 2026.10 reaches EOL on December 29, 2026 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Dec 29, 2026
60 days remaining
Latest Release
2026.10.0
Standard release
Release Date
Oct 27, 2026
Discourse 2026.10 series
Where these dates come from
End of lifeDec 29, 2026endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseOct 27, 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
Discourse 2026.10 was released on October 27, 2026 and support is scheduled to end on December 29, 2026 — a planned supported lifespan of 2 months, in line with the 2 months median for Discourse releases. It is not an LTS release; Discourse reserves longer patch windows for its LTS versions. Its most recent patch is 2026.10.0, published October 27, 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 Discourse 2026.10 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 |
|---|
| 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.9 |
Sep 22, 2026 |
EOL |
| 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 2026.10 end of life mean?
When Discourse 2026.10 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 Discourse 2026.10 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
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 2026.10 reach end of life?
Discourse 2026.10 reaches end of life on December 29, 2026. That is 60 days remaining.
Is Discourse 2026.10 still supported?
Discourse 2026.10 is still supported but approaching end of life on December 29, 2026. Begin planning your migration now.
What should I upgrade to from Discourse 2026.10?
What are the security risks of running Discourse 2026.10 past EOL?
When Discourse 2026.10 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 Discourse should migrate immediately or implement compensating controls.