Apache Pulsar 3.3
Apache Pulsar 3.3
The Apache Pulsar 3.3 reached end of service life on Dec 5, 2024 — Apache Pulsar no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your Apache Pulsar 3.3 incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- apache-pulsar
- release
- 3.3
- product Label
- Apache Pulsar
- release Label
- 3.3
- codename
- lts
- latest Version
- 3.3.9
- release Date
- 2024-06-05
- maintained
- source Url
- https://endoflife.date/apache-pulsar
Lifecycle Dates
- End of Service Life
- Dec 5, 2024
- Last OEM Support
- Dec 5, 2024
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Apache Pulsar 3.3 — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for Apache Pulsar 3.3?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Apache Pulsar 3.3 when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
Apache Pulsar 3.3 Support: Frequently Asked Questions
Is the Apache Pulsar 3.3 still supported?
Apache Pulsar ended support for the Apache Pulsar 3.3 on Dec 5, 2024 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the Apache Pulsar 3.3 end of service life (EOSL) date?
Apache Pulsar lists the end of service life for the Apache Pulsar 3.3 as Dec 5, 2024.
Can I keep using the Apache Pulsar 3.3 after its EOSL date?
Yes. EOSL means Apache Pulsar stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the Apache Pulsar 3.3 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting Apache Pulsar 3.3
1 published CVE affects the Apache Pulsar 3.3. Apache Pulsar no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2025-30677 | MEDIUM | 6.3 | Apr 9, 2025 | Apache Pulsar contains multiple connectors for integrating with Apache Kafka. The Pulsar IO Apache Kafka Source Connector, Sink Connector, and Kafka Connect Adaptor Sink Connector log sensitive configuration properties in plain text in application logs. This vulnerability can lead to unintended exposure of credentials in log files, potentially allowing attackers with access to these logs to obtain Apache Kafka credentials. The vulnerability's impact is limited by the fact that an attacker woul |