Apache Kafka 3.3 · Version Status
Apache Kafka 3.3 End of Life Date
Apache Kafka 3.3 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 Kafka 3.3 is past end of life. This version no longer receives security patches. 1348 days past EOL — migrate to a supported version immediately.
EOL Date
Feb 6, 2023
1348 days past EOL
Latest Release
3.3.2
Standard release
Release Date
Sep 28, 2022
Apache Kafka 3.3 series
Extended Support
Nov 4, 2024
Extended support · ended
Lifecycle detail
Apache Kafka 3.3 was released on September 28, 2022 and support ended on February 6, 2023 — a supported lifespan of 4 months, shorter than the 6 months median for Apache Kafka releases. The last patch it will ever receive is 3.3.2, published January 11, 2023 — 26 days before support ended. It has been without security patches for 3 years and 8 months. 10 newer Apache Kafka 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 Kafka 3.3 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
All Apache Kafka Versions
| Version | Latest | EOL Date | Status |
|---|
| 0.7 |
0.7.2 |
Dec 3, 2013 |
EOL |
| 0.8 |
0.8.2.2 |
Nov 23, 2015 |
EOL |
| 0.9 |
0.9.0.1 |
May 22, 2016 |
EOL |
| 0.10 |
0.10.2.2 |
Jul 2, 2018 |
EOL |
| 0.11 |
0.11.0.3 |
Jul 2, 2018 |
EOL |
| 1.0 |
1.0.2 |
Jul 8, 2018 |
EOL |
| 1.1 |
1.1.1 |
Jul 30, 2018 |
EOL |
| 2.0 |
2.0.1 |
Nov 20, 2018 |
EOL |
What does Apache Kafka 3.3 end of life mean?
When Apache Kafka 3.3 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 Kafka 3.3 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Apache Kafka 4.3 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Apache Kafka 3.3 reach end of life?
Apache Kafka 3.3 reached end of life on February 6, 2023. This version is no longer receiving security patches.
Is Apache Kafka 3.3 still supported?
No. Apache Kafka 3.3 reached end of life on February 6, 2023 and is no longer receiving security patches.
What should I upgrade to from Apache Kafka 3.3?
The recommended upgrade from Apache Kafka 3.3 is
Apache Kafka 4.3 — the latest actively supported version. Check the
Apache Kafka full timeline for all supported versions.
What are the security risks of running Apache Kafka 3.3 past EOL?
When Apache Kafka 3.3 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 Kafka should migrate immediately or implement compensating controls.