Apache Pulsar 2.x — End of Life

EOL
EOL: Jan 11, 20247 releases in this series0 CVEs

Apache Pulsar 2.x — All releases

VersionReleasedActive supportEOL dateLatest patchStatus
2.11Jan 11, 2023Jan 11, 20242.11.4EOL
2.10Apr 18, 2022Apr 18, 20232.10.6EOL
2.9Dec 20, 2021Dec 20, 20222.9.5EOL
2.8Jun 15, 2021Jun 15, 20222.8.4EOL
2.7Dec 3, 2020Dec 3, 20212.7.5EOL
2.6Jun 17, 2020Jun 17, 20212.6.4EOL
2.5Jan 15, 2020Jan 15, 20212.5.2EOL

CVEs affecting Apache Pulsar 2.x (0)

No CVEs tracked for Apache Pulsar 2.x.

Apache Pulsar 2.x is EOL — migrate to Apache Pulsar 3.x

Apache Pulsar 3.x is the next major release. Plan your upgrade before Apache Pulsar 2.x stops receiving security patches.

See Apache Pulsar 3.x

Frequently asked questions

Is Apache Pulsar 2 end of life?

Yes. All Apache Pulsar 2.x releases have reached end of life and no longer receive security patches. Migrate to Apache Pulsar 3.x as soon as possible.

What CVEs affect Apache Pulsar 2?

No CVEs are currently tracked for Apache Pulsar 2.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 2 version?

The latest Apache Pulsar 2.x patch release is 2.11.4, released on March 8, 2024. Always run the latest patch to benefit from all security fixes.

How to migrate from Apache Pulsar 2 to Apache Pulsar 3?

To migrate from Apache Pulsar 2 to Apache Pulsar 3: (1) review the official Apache Pulsar 3 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 2 in production?

No. Apache Pulsar 2 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