Apache Pulsar 2.11 · Version Status
Apache Pulsar 2.11 End of Life Date
Apache Pulsar 2.11 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
Apache Pulsar 2.11 is past end of life. This version no longer receives security patches. 1001 days past EOL — migrate to a supported version immediately.
EOL Date
Jan 11, 2024
1001 days past EOL
Latest Release
2.11.4
Standard release
Release Date
Jan 11, 2023
Apache Pulsar 2.11 series
Lifecycle detail
Apache Pulsar 2.11 was released on January 11, 2023 and support ended on January 11, 2024 — a supported lifespan of 1 year, in line with the 1 year median for Apache Pulsar releases. It was not an LTS release; Apache Pulsar reserves longer patch windows for its LTS versions. The last patch it will ever receive is 2.11.4, published March 8, 2024 — 2 months after the published end-of-life date. It has been without security patches for 2 years and 9 months. 6 newer Apache Pulsar releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended Apache Pulsar 2.11 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
All Apache Pulsar Versions
| Version | Latest | EOL Date | Status |
|---|
| 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 2.11 end of life mean?
When Apache Pulsar 2.11 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Apache Pulsar 2.11 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Apache Pulsar 5.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Apache Pulsar 2.11 reach end of life?
Apache Pulsar 2.11 reached end of life on January 11, 2024. This version is no longer receiving security patches.
Is Apache Pulsar 2.11 still supported?
No. Apache Pulsar 2.11 reached end of life on January 11, 2024 and is no longer receiving security patches.
What should I upgrade to from Apache Pulsar 2.11?
The recommended upgrade from Apache Pulsar 2.11 is
Apache Pulsar 5.0 — the latest actively supported version. Check the
Apache Pulsar full timeline for all supported versions.
What are the security risks of running Apache Pulsar 2.11 past EOL?
When Apache Pulsar 2.11 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Apache Pulsar should migrate immediately or implement compensating controls.