# Path Traversal in Apache Flink

Advisory record · `GHSA-395w-qhqr-9fr6`

- **Identifiers:** `GHSA-395w-qhqr-9fr6` · `BIT-flink-2020-17519` · `CVE-2020-17519`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** Yes: KEV, CVSS 7+ and EPSS
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html) · [CWE-552](https://cwe.mitre.org/data/definitions/552.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md) · [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 6 Jan 2021
- **Updated:** 22 Oct 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 6 Jan 2021, 20:01 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- In CISA’s KEV catalogue since 23 May 2024: it is known to be exploited.
- CVSS score 7.5 (7.0 or more) and EPSS 0.98 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `org.apache.flink:flink-runtime_2.11` (Maven): affected `>=1.11.0, <1.11.3`; fixed in `1.11.3`
- `org.apache.flink:flink-runtime_2.12` (Maven): affected `>=1.11.0, <1.11.3`; fixed in `1.11.3`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache Flink's flink-runtime_2.11 and flink-runtime_2.12 packages, versions 1.11.0 through 1.11.2, are affected by a path traversal flaw. An attacker with access to the JobManager's REST interface can read any file the JobManager process can access on the local filesystem. Upgrade to flink-runtime 1.11.3 or later, or to Flink 1.12.0, especially if the instance is exposed.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:H`, from GitHub Advisory Database

- **CISA KEV:** Listed since 23 May 2024: known to be exploited.
- **EPSS:** 0.98, the 99th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:10 UTC: First seen by agentprime
- 31 Oct 2026, 15:10 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-395w-qhqr-9fr6)

## Sources

- [GitHub Advisory Database: GHSA-395w-qhqr-9fr6](https://github.com/advisories/GHSA-395w-qhqr-9fr6)
- [OSV: GHSA-395w-qhqr-9fr6](https://osv.dev/vulnerability/GHSA-395w-qhqr-9fr6)
- <https://nvd.nist.gov/vuln/detail/CVE-2020-17519>
- <https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-17519>
- <https://lists.apache.org/thread.html/ra8c96bf3ccb4e491f9ce87ba35f134b4449beb2a38d1ce28fd89001f@%3Cdev.flink.apache.org%3E>
- <https://lists.apache.org/thread.html/ra8c96bf3ccb4e491f9ce87ba35f134b4449beb2a38d1ce28fd89001f%40%3Cdev.flink.apache.org%3E>
- <https://lists.apache.org/thread.html/r90890afea72a9571d666820b2fe5942a0a5f86be406fa31da3dd0922@%3Cannounce.apache.org%3E>
- <https://lists.apache.org/thread.html/r90890afea72a9571d666820b2fe5942a0a5f86be406fa31da3dd0922%40%3Cannounce.apache.org%3E>
- <https://lists.apache.org/thread.html/r88f427865fb6aa6e6378efe07632a1906b430365e15e3b9621aabe1d@%3Cissues.flink.apache.org%3E>
- <https://lists.apache.org/thread.html/r88f427865fb6aa6e6378efe07632a1906b430365e15e3b9621aabe1d%40%3Cissues.flink.apache.org%3E>
- <https://lists.apache.org/thread.html/r88b55f3ebf1f8f4e1cc61f030252aaef4b77060b56557a243abb92a1@%3Cissues.flink.apache.org%3E>
- <https://lists.apache.org/thread.html/r88b55f3ebf1f8f4e1cc61f030252aaef4b77060b56557a243abb92a1%40%3Cissues.flink.apache.org%3E>
- <https://lists.apache.org/thread.html/r6843202556a6d0bce9607ebc02e303f68fc88e9038235598bde3b50d@%3Cuser.flink.apache.org%3E>
- <https://lists.apache.org/thread.html/r6843202556a6d0bce9607ebc02e303f68fc88e9038235598bde3b50d@%3Cdev.flink.apache.org%3E>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-395w-qhqr-9fr6>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-395w-qhqr-9fr6/>. Everything for agents: <https://agentprime.io/llms.txt>.
