CometD End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all CometD versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 5.0 | 5.0.21 | Apr 16, 2020 | Sep 1, 2022 | 1422 days past EOL | EOL |
| 6.0 | 6.0.17 | Dec 21, 2020 | Sep 1, 2024 | 691 days past EOL | EOL |
| 7.0 | 7.0.17 | Dec 21, 2020 | Sep 1, 2024 | 691 days past EOL | EOL |
| 8.0 | 8.0.12 | May 16, 2024 | TBD | Supported | Active |
| 9.0 | 9.0.1 | Oct 10, 2025 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/cometd)
CometD lifecycle status — the real story
CometD, the Java implementation of the Bayeux protocol for WebSocket and long-polling messaging, manages lifecycle transitions unusually formally for a community project: End of Community Support is announced in advance, in writing. CometD 5.0.x reached that milestone on September 1 2022, and 6.0.x and 7.0.x followed on September 1 2024 — each tracking the matching Jetty version's retirement. The 8.0.x and 9.0.x lines are the actively maintained releases.
"End of Community Support" means exactly what it says: security and critical-fix releases after those dates exist only for commercial-support customers of Webtide, the core maintainers. The final community releases of the 5/6/7 lines shipped in September 2024; organizations still on them are running an unpatched real-time messaging layer.
The long tail here is bigger than the project's profile suggests: CometD underpins Salesforce's Streaming API clients, trading platforms, and collaboration tools where a protocol-level flaw in Bayeux message handling or WebSocket transport reaches everything downstream. Extended support for the 5, 6, and 7 lines is available commercially — including through the maintainers' own partnership channel — for teams that cannot re-platform their messaging tier quickly.
What does CometD end of life mean for your organization?
When a version of CometD 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 CometD 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL CometD versions. This is a bridge, not a permanent solution — plan your migration in parallel.
CometD has 3 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for CometD exists — vetted vendors ship security patches for years past the official date. Right now that coverage spans CometD 5, 6, 7. Tell us where to reach you and we'll reply with matched options and pricing guidance.