CVE-2020-17519
CriticalExploitedPublic exploitPath Traversal in Apache Flink
Published Jan 6, 2021 · Updated Sep 10, 2026 · Also known as BIT-flink-2020-17519, GHSA-395w-qhqr-9fr6
Key Facts
Patch immediately- CVE-2020-17519 is a critical-severity vulnerability (CVSS 9.1 v3.1) affecting Flink (Apache), org.apache.flink:flink-runtime_2.11 (maven), org.apache.flink:flink-runtime_2.12 (maven).
- It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Apr 12, 2021. Public exploit code is available.
- EPSS estimates a 98% probability of exploitation in the next 30 days.
- Fixed versions are available, including Flink 1.11.3, org.apache.flink:flink-runtime_2.11 1.11.3, org.apache.flink:flink-runtime_2.12 1.11.3.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
CVSS v3.1
9.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
EPSS (30-day exploit likelihood)
98%
Higher than 99.9% of all scored CVEs
Exploited in the wild
Yes
4 catalog listings
Public exploit code
Available
Proof-of-concept or weaponized module
Get the full CVE-2020-17519 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
Description
A change introduced in Apache Flink 1.11.0 (and released in 1.11.1 and 1.11.2 as well) allows attackers to read any file on the local filesystem of the JobManager through the REST interface of the JobManager process. Access is restricted to files accessible by the JobManager process. All users should upgrade to Flink 1.11.3 or 1.12.0 if their Flink instance(s) are exposed. The issue was fixed in commit b561010b0ee741543c3953306037f00d7a9f0801 from apache/flink:master.
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| CISA KEV | May 23, 2024 | Jun 13, 2024 | Not reported |
| Industry KEV feed | Apr 12, 2021 | Jun 13, 2024 | Not reported |
| CIRCL KEV | Oct 14, 2023 | Jun 13, 2024 | Not reported |
| ENISA EUVD | May 23, 2024 | n/a | Not reported |
Required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Affected Products
5 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| FlinkApache | >= 1.11.0, >= Apache Flink 1.11.0 to 1.11.2 | 1.11.3 |
| org.apache.flink:flink-runtime_2.11maven | >= 1.11.0 | 1.11.3 |
| org.apache.flink:flink-runtime_2.12maven | >= 1.11.0 | 1.11.3 |
Patched Releases
Flink
1.11.3
org.apache.flink:flink-runtime_2.11
1.11.3
org.apache.flink:flink-runtime_2.12
1.11.3
Timeline
Publicly disclosed
Jan 6, 2021
Added to Industry KEV feed
Apr 12, 2021
Added to CIRCL KEV
Oct 14, 2023
Added to CISA KEV
May 23, 2024
Added to ENISA EUVD
May 23, 2024
Last updated
Sep 10, 2026
Weakness Type
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CWE-552 Files or Directories Accessible to External Parties
References
- advisoryGHSA advisory
- advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2020-17519
- exploitVulnCheck exploitation report
- exploitVulnCheck exploitation report
- exploitVulnCheck exploitation report
FAQ
Common Questions.
A change introduced in Apache Flink 1.11.0 (and released in 1.11.1 and 1.11.2 as well) allows attackers to read any file on the local filesystem of the JobManager through the REST interface of the JobManager process.
Affected: Flink (Apache) versions >= 1.11.0, >= Apache Flink 1.11.0 to 1.11.2; org.apache.flink:flink-runtime_2.11 (maven) versions >= 1.11.0; org.apache.flink:flink-runtime_2.12 (maven) versions >= 1.11.0. The full list is in the CVE brief.
It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Apr 12, 2021.
Yes. It was added on May 23, 2024 with a federal remediation due date of Jun 13, 2024.
Public exploit code is available.
Fixed versions are available, including Flink 1.11.3, org.apache.flink:flink-runtime_2.11 1.11.3, org.apache.flink:flink-runtime_2.12 1.11.3.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2020-17519 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo