Apache Flink 2.0 · Version Status

Apache Flink 2.0 End of Life Date

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

Apache Flink 2.0 is actively supported. EOL date: Already EOL.
EOL Date
Already EOL
Supported
Latest Release
2.0.2
Standard release
Release Date
Mar 19, 2025
Apache Flink 2.0 series
← Apache Flink 1.20 All Apache Flink versions Apache Flink 2.1 →
All Apache Flink Versions
VersionLatestEOL DateStatus
1.17 1.17.2 Aug 1, 2024 EOL
1.18 1.18.1 Mar 24, 2025 EOL
1.19 1.19.3 EOL Active
1.20 LTS 1.20.4 EOL Active
2.0 2.0.2 EOL Active
2.1 2.1.1 EOL Active
2.2 2.2.0 EOL Active

What does Apache Flink 2.0 end of life mean?

When Apache Flink 2.0 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 Flink 2.0 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

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

Frequently Asked Questions
When does Apache Flink 2.0 reach end of life?
Apache Flink 2.0 has already reached end of life.
Is Apache Flink 2.0 still supported?
Yes, Apache Flink 2.0 is currently supported. The EOL date is Already EOL.
What should I upgrade to from Apache Flink 2.0?
The recommended upgrade from Apache Flink 2.0 is Apache Flink 2.2 — the latest actively supported version. Check the Apache Flink full timeline for all supported versions.
What are the security risks of running Apache Flink 2.0 past EOL?
When Apache Flink 2.0 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 Flink should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →