Apache Kafka 4.2 · Version Status

Apache Kafka 4.2 End of Life Date

Apache Kafka 4.2 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Apache Kafka 4.2 is actively supported. EOL date: Already EOL.
EOL Date
Already EOL
Supported
Latest Release
4.2.0
Standard release
Release Date
Feb 17, 2026
Apache Kafka 4.2 series
← Apache Kafka 4.1 All Apache Kafka versions
All Apache Kafka Versions
VersionLatestEOL DateStatus
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 4.2 end of life mean?

When Apache Kafka 4.2 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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Apache Kafka 4.2 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Apache Kafka 4.2 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Apache Kafka 4.2 reach end of life?
Apache Kafka 4.2 has already reached end of life.
Is Apache Kafka 4.2 still supported?
Yes, Apache Kafka 4.2 is currently supported. The EOL date is Already EOL.
What should I upgrade to from Apache Kafka 4.2?
The recommended upgrade from Apache Kafka 4.2 is Apache Kafka 4.2 — the latest actively supported version. Check the Apache Kafka full timeline for all supported versions.
What are the security risks of running Apache Kafka 4.2 past EOL?
When Apache Kafka 4.2 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Apache Kafka should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →