Apache Flink 1.17 · Version Status
Apache Flink 1.17 End of Life Date
Apache Flink 1.17 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Apache Flink 1.17 is past end of life. This version no longer receives security patches. 747 days past EOL — migrate to a supported version immediately.
EOL Date
Aug 1, 2024
747 days past EOL
Latest Release
1.17.2
Standard release
Release Date
Mar 23, 2023
Apache Flink 1.17 series
Lifecycle detail
Apache Flink 1.17 was released on March 23, 2023 and support ended on August 1, 2024 — a supported lifespan of 1 year and 4 months, in line with the 1 year and 5 months median for Apache Flink releases. It was not an LTS release; Apache Flink reserves longer patch windows for its LTS versions. The last patch it will ever receive is 1.17.2, published November 27, 2023 — 8 months before support ended. It has been without security patches for 2 years and 1 month. 4 newer Apache Flink releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA 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 Flink 1.17 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
All Apache Flink Versions
| Version | Latest | EOL Date | Status |
|---|
| → 1.17 |
1.17.2 |
Aug 1, 2024 |
EOL |
| 1.18 |
1.18.1 |
Mar 24, 2025 |
EOL |
| 1.19 |
1.19.3 |
Jul 1, 2026 |
EOL |
| 1.20 LTS |
1.20.5 |
EOL |
Active |
| 2.0 |
2.0.2 |
Jun 25, 2026 |
EOL |
| 2.1 |
2.1.3 |
EOL |
Active |
| 2.2 |
2.2.1 |
EOL |
Active |
| 2.3 |
2.3.0 |
EOL |
Active |
What does Apache Flink 1.17 end of life mean?
When Apache Flink 1.17 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 1.17 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Apache Flink 2.3 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Apache Flink 1.17 reach end of life?
Apache Flink 1.17 reached end of life on August 1, 2024. This version is no longer receiving security patches.
Is Apache Flink 1.17 still supported?
No. Apache Flink 1.17 reached end of life on August 1, 2024 and is no longer receiving security patches.
What should I upgrade to from Apache Flink 1.17?
The recommended upgrade from Apache Flink 1.17 is
Apache Flink 2.3 — the latest actively supported version. Check the
Apache Flink full timeline for all supported versions.
What are the security risks of running Apache Flink 1.17 past EOL?
When Apache Flink 1.17 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.