Complete end-of-life dates, support windows, and security status for all Apache Pulsar versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2.5 | 2.5.2 | Jan 15, 2020 | Jan 15, 2021 | 1940 days past EOL | EOL |
| 2.6 | 2.6.4 | Jun 17, 2020 | Jun 17, 2021 | 1787 days past EOL | EOL |
| 2.7 | 2.7.5 | Dec 3, 2020 | Dec 3, 2021 | 1618 days past EOL | EOL |
| 2.8 | 2.8.4 | Jun 15, 2021 | Jun 15, 2022 | 1424 days past EOL | EOL |
| 2.9 | 2.9.5 | Dec 20, 2021 | Dec 20, 2022 | 1236 days past EOL | EOL |
| 2.10 | 2.10.6 | Apr 18, 2022 | Apr 18, 2023 | 1117 days past EOL | EOL |
| 2.11 | 2.11.4 | Jan 11, 2023 | Jan 11, 2024 | 849 days past EOL | EOL |
| 3.0 LTS | 3.0.17 | May 2, 2023 | May 2, 2025 | 372 days past EOL | EOL |
| 3.1 | 3.1.3 | Aug 10, 2023 | Feb 10, 2024 | 819 days past EOL | EOL |
| 3.2 | 3.2.4 | Feb 5, 2024 | Aug 5, 2024 | 642 days past EOL | EOL |
| 3.3 | 3.3.9 | Jun 5, 2024 | Dec 5, 2024 | 520 days past EOL | EOL |
| 4.0 LTS | 4.0.10 | Oct 21, 2024 | Oct 21, 2026 | 165 days remaining | Warning |
| 4.1 | 4.1.3 | Sep 8, 2025 | Mar 8, 2026 | 62 days past EOL | EOL |
| 4.2 | 4.2.1 | Mar 24, 2026 | Sep 24, 2026 | 138 days remaining | Warning |
When a Apache Pulsar version 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 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →