Synced 07 Nov 2026 15:45 UTC Account
← All products

Flink ↗

Apache · Actively exploited
↻ RSS feed
Monitors Flink and tailors your dashboard to that exact version.
2.3.0 · latest cycle100/100 Healthy
⚡ Newly tracked. IsItPatched added Flink automatically when CISA flagged it as actively exploited — its data is fresh and being verified.

Auto-added after CISA flagged Flink as actively exploited (KEV catalog). Version and lifecycle mapping is pending review, so this is assessed at the product level and is never reported as a confident "healthy".

Summary iPlain-English security verdict for Flink, generated from its current health score, actively-exploited vulnerabilities, and latest supported version.

Flink currently scores 100/100 — healthy. 1 actively-exploited vulnerability (CISA KEV) affects older releases (e.g. CVE-2020-17519) — staying on the latest supported version keeps you clear of it. The latest supported release is 2.3.0. It's on the latest patch with no significant known issues — keep it current.

The known vulnerabilities

IsItPatched tracks 4 known vulnerabilities in Apache Flink disclosed between 2020 and 2026. CVE-2020-1960 is a medium-severity vulnerability (CVSS 4.7). CVE-2020-17518 is a high-severity path traversal vulnerability (CVSS 7.5). CVE-2020-17519 is a high-severity vulnerability (CVSS 7.5), which is actively exploited in the wild (CISA KEV). CVE-2026-35194 is a high-severity code injection vulnerability (CVSS 8.1). Move to a patched, supported release — this issue is being exploited in the wild, so treat it as urgent.

Disclosure trend iNew CVEs published for Flink each year (NVD). A higher bar means more disclosures that year — more scrutiny, not necessarily less safe.

'19
'20
'21
'22
'23
'24
'25
'26

Patch priority — what to act on iThe issues to fix first — actively exploited (CISA KEV) first, then by exploitation probability (EPSS), then severity. Each row's "→ fixed in" is the earliest version that patches it; "see advisory" means no fixed version is published.

Most urgent first — actively exploited, then likeliest to be exploited.

CVE-2020-17519 HIGH exploited CWE-552 EPSS 98% → fixed in 1.11.3 CVE-2020-17518 HIGH Path traversal EPSS 49% → fixed in 1.11.3

Get alerted about Flink

Be emailed the moment Flink gets a newly exploited vulnerability (CISA KEV) or a release reaches end of life. Free · double opt-in · unsubscribe anytime.

We email only on real events for Flink — no marketing, no sharing, and we never know what you run. Track your whole stack →

★ Monitor up to 200 products — freeHit ☆ Monitor on anything you run, then sign in (no password) to sync your stack across devices and unlock smart insights, risk history & CSV/JSON exports. Sign in free →

Versions & lifecycle iWhen each release line stops receiving security patches (end-of-life). After EOL there are no more fixes — plan upgrades before these dates.

How long each Flink release line is supported — and when it sunsets. Select a line for its full report.

Jul1'26 Flink 1.19ended 2026-07-01
Jun25'26 Flink 2.0ended 2026-06-25
Mar24'25 Flink 1.18ended 2025-03-24
Aug1'24 Flink 1.17ended 2024-08-01

Full Flink end-of-life dates & support timeline →

2.3 latest 2.3.0 Supported 2.3.0 → 2.2 latest 2.2.1 Supported 2.2.1 → 2.1 latest 2.1.3 Supported 2.1.3 → 2.0 latest 2.0.2 End of life ended 2026-06-252.0.2 → 1.20 latest 1.20.5 Supported 1.20.5 → 1.19 latest 1.19.3 End of life ended 2026-07-011.19.3 → 1.18 latest 1.18.1 End of life ended 2025-03-241.18.1 → 1.17 latest 1.17.2 End of life ended 2024-08-011.17.2 → See all upcoming end-of-life dates →

Frequently asked

Is Flink safe and patched?

Flink currently scores 100/100 — healthy. 1 actively-exploited vulnerability (CISA KEV) affects older releases (e.g. CVE-2020-17519) — staying on the latest supported version keeps you clear of it. The latest supported release is 2.3.0. It's on the latest patch with no significant known issues — keep it current.

What should I do about Flink now?

Upgrade Flink to the latest supported release (2.3.0) or later, which clears the actively-exploited issues affecting older versions, then confirm against Apache's official advisory.

Why is Flink listed on IsItPatched?

Flink was added automatically because CISA's Known Exploited Vulnerabilities (KEV) catalog flagged it as actively exploited in the wild. IsItPatched tracks its known CVEs, severity (CVSS), exploitation probability (EPSS) and KEV status from public data; its version and lifecycle mapping is verified over time.

Has Flink been actively exploited?

Yes. CISA added Flink to its Known Exploited Vulnerabilities (KEV) catalog after confirming exploitation in the wild — the triggering vulnerability is CVE-2020-17519. Make sure you are running a patched, supported version of Flink and confirm it against Apache's security advisory.

When does Flink reach end-of-life?

The latest supported Flink release is 2.3.0. After end-of-life a release no longer receives security patches.

Which versions of Flink are still receiving security updates?

Supported Flink release lines (latest 2.3.0): 2.3, 2.2, 2.1, 1.20. End-of-life releases no longer receive security patches.

Similar software we track

More from Apache tracked on IsItPatched.

Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against Apache's official advisory before you patch or upgrade — Flink official site ↗