Exploited CVEs / Apache / CVE-2020-17519
CVE-2020-17519
Apache Flink Improper Access Control Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2024-06-13 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.
Actively exploited Apache Flink vulnerability, High severity, CVSS 7.5. Added to the CISA KEV catalog 2024-05-23.
Risk summary
Updated July 27, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Senserva AI Opinion for CVE-2020-17519
Apache Flink's JobManager REST interface can be tricked into serving any file the process can read on the local filesystem, no authentication involved. With a 98 percent EPSS probability and a May 2024 KEV listing, exploitation is effectively guaranteed for exposed instances. Data-platform components like Flink often keep credentials in configuration files, exactly what this flaw hands over.
Do this: Ensure Flink JobManager REST interfaces are unreachable from untrusted networks and upgrade past the CVE-2020-17519 fix.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2020-17519
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for CVE-2020-17519
Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.
CISA required action
Federal (BOD 22-01) remediation due date: 2024-06-13 (past due).
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Official fix for CVE-2020-17519
Check the vendor's security advisory channel for the patched Flink versions and workarounds.
Common questions about CVE-2020-17519
Is CVE-2020-17519 actively exploited?
Yes. CVE-2020-17519 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2024-05-23, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 98%.
What is the CISA deadline and required action for CVE-2020-17519?
CISA set the federal (BOD 22-01) remediation due date at 2024-06-13, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
What fixes CVE-2020-17519?
Check the vendor's security advisory for the patched Flink versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.
Can I ask my own AI about CVE-2020-17519?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2020-17519's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).
More exploited Apache CVEs
The newest Apache entries on the CISA KEV catalog:
All Apache exploited CVEs on one page: Apache vulnerabilities actively exploited.
Authoritative references
Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.
