Apache Pulsar 4.0 · Version Status

Apache Pulsar 4.0 End of Life Date

Apache Pulsar 4.0 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Apache Pulsar 4.0 reaches end of life on October 21, 2026. Plan your migration now — 165 days remaining.
EOL Date
Oct 21, 2026
165 days remaining
Latest Release
4.0.10
LTS release
Release Date
Oct 21, 2024
Apache Pulsar 4.0 series
← Apache Pulsar 3.3 All Apache Pulsar versions Apache Pulsar 4.1 →
All Apache Pulsar Versions
VersionLatestEOL DateStatus
2.5 2.5.2 Jan 15, 2021 EOL
2.6 2.6.4 Jun 17, 2021 EOL
2.7 2.7.5 Dec 3, 2021 EOL
2.8 2.8.4 Jun 15, 2022 EOL
2.9 2.9.5 Dec 20, 2022 EOL
2.10 2.10.6 Apr 18, 2023 EOL
2.11 2.11.4 Jan 11, 2024 EOL
3.0 LTS 3.0.17 May 2, 2025 EOL

What does Apache Pulsar 4.0 end of life mean?

When Apache Pulsar 4.0 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 Apache Pulsar 4.0 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 Apache Pulsar 4.0 reach end of life?
Apache Pulsar 4.0 reached end of life on October 21, 2026. That is 165 days remaining.
Is Apache Pulsar 4.0 still supported?
Apache Pulsar 4.0 is still supported but approaching end of life on October 21, 2026. Begin planning your migration now.
What should I upgrade to from Apache Pulsar 4.0?
Check the Apache Pulsar full timeline for currently supported versions.
What are the security risks of running Apache Pulsar 4.0 past EOL?
When Apache Pulsar 4.0 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 Apache Pulsar should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →