Apache Pulsar 3.x — End of Life
EOLApache Pulsar 3.x — All releases
| Version | Released | Active support | EOL date | Latest patch | Status |
|---|---|---|---|---|---|
| 3.3 | Jun 5, 2024 | — | Dec 5, 2024 | 3.3.9 | EOL |
| 3.2 | Feb 5, 2024 | — | Aug 5, 2024 | 3.2.4 | EOL |
| 3.1 | Aug 10, 2023 | — | Feb 10, 2024 | 3.1.3 | EOL |
| 3.0LTS | May 2, 2023 | — | May 2, 2025 | 3.0.17 | EOL |
CVEs affecting Apache Pulsar 3.x (0)
Apache Pulsar 3.x is EOL — migrate to Apache Pulsar 4.x
Apache Pulsar 4.x is the next major release. Plan your upgrade before Apache Pulsar 3.x stops receiving security patches.
Frequently asked questions
Is Apache Pulsar 3 end of life?
Yes. All Apache Pulsar 3.x releases have reached end of life and no longer receive security patches. Migrate to Apache Pulsar 4.x as soon as possible.
What CVEs affect Apache Pulsar 3?
No CVEs are currently tracked for Apache Pulsar 3.x in our database. This may mean no vulnerabilities have been recorded yet, or the data is still syncing.
What is the latest Apache Pulsar 3 version?
The latest Apache Pulsar 3.x patch release is 3.3.9, released on September 27, 2025. Always run the latest patch to benefit from all security fixes.
How to migrate from Apache Pulsar 3 to Apache Pulsar 4?
To migrate from Apache Pulsar 3 to Apache Pulsar 4: (1) review the official Apache Pulsar 4 migration guide for breaking changes, (2) update dependencies and configuration accordingly, (3) test thoroughly in a staging environment, (4) deploy with a rollback plan. Starting early gives you time to resolve compatibility issues before your current version reaches end of life.
Is it safe to run Apache Pulsar 3 in production?
No. Apache Pulsar 3 has reached end of life and security vulnerabilities are no longer patched. Upgrade to a supported version immediately.
Data sourced from endoflife.date · CVE data from NVD · EPSS from FIRST.org · KEV from CISA