Apache Pulsar End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Apache Pulsar versions. Data from endoflife.date, checked against the vendor's own lifecycle pages where we have read them (share on /accuracy). Updated at every deploy.
Apache Pulsar 5.0 is supported until October 5, 2028, its end-of-support date. It is also the next Apache Pulsar version to reach end of life. 14 of 15 tracked Apache Pulsar versions are past end of life; the most recent to reach it, 4.0, did so on October 21, 2026. The full Apache Pulsar lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Extended Support | Days | Status |
|---|---|---|---|---|---|---|
| 2.5 | 2.5.2 | Jan 15, 2020 | Jan 15, 2021 | — | 2122 days past EOL | EOL |
| 2.6 | 2.6.4 | Jun 17, 2020 | Jun 17, 2021 | — | 1969 days past EOL | EOL |
| 2.7 | 2.7.5 | Dec 3, 2020 | Dec 3, 2021 | — | 1800 days past EOL | EOL |
| 2.8 | 2.8.4 | Jun 15, 2021 | Jun 15, 2022 | — | 1606 days past EOL | EOL |
| 2.9 | 2.9.5 | Dec 20, 2021 | Dec 20, 2022 | — | 1418 days past EOL | EOL |
| 2.10 | 2.10.6 | Apr 18, 2022 | Apr 18, 2023 | — | 1299 days past EOL | EOL |
| 2.11 | 2.11.4 | Jan 11, 2023 | Jan 11, 2024 | — | 1031 days past EOL | EOL |
| 3.0 LTS | 3.0.17 | May 2, 2023 | May 2, 2025 | May 2, 2026 Extended support (ended) |
554 days past EOL | EOL |
| 3.1 | 3.1.3 | Aug 10, 2023 | Feb 10, 2024 | — | 1001 days past EOL | EOL |
| 3.2 | 3.2.4 | Feb 5, 2024 | Aug 5, 2024 | — | 824 days past EOL | EOL |
| 3.3 | 3.3.9 | Jun 5, 2024 | Dec 5, 2024 | — | 702 days past EOL | EOL |
| 4.0 LTS | 4.0.14 | Oct 21, 2024 | Oct 21, 2026 | Oct 21, 2027 Extended support |
17 days past EOL | EOL |
| 4.1 | 4.1.3 | Sep 8, 2025 | Mar 8, 2026 | — | 244 days past EOL | EOL |
| 4.2 | 4.2.5 | Mar 24, 2026 | Sep 24, 2026 | — | 44 days past EOL | EOL |
| 5.0 LTS | 5.0.1 | Oct 5, 2026 | Oct 5, 2028 | Oct 5, 2029 Extended support |
698 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/apache-pulsar)
Apache Pulsar release and support pattern
Across the 15 release lines with a published release date, Apache Pulsar has shipped a new line roughly every 6 months (median interval). A line typically stays in standard support for about 1 year from its release to its standard-support end date. 3 of the 15 tracked lines are designated long-term support, which is where the longer windows sit.
Of the 15 release lines tracked, 14 are past end of life and 1 is still within support. The newest line, 5.0, was released October 5, 2026. The next scheduled end of life is 5.0 on October 5, 2028 — 697 days from this build. Upstream also publishes an extended-support phase for 15 lines, shown in the table above.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Apache Pulsar end of life mean for your organization?
When a version of Apache Pulsar 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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Apache Pulsar 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.
Your options when Apache Pulsar reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, check whether the vendor or a third party sells extended support with security patches for your Apache Pulsar version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.
Apache Pulsar has 14 versions past end of life — standard security patches have stopped; 1 of them is still covered by Extended support, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Apache Pulsar is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."