How severe is GHSA-395w-qhqr-9fr6?

GHSA-395w-qhqr-9fr6 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-395w-qhqr-9fr6?

GHSA-395w-qhqr-9fr6 affects the following packages: org.apache.flink:flink-runtime_2.11 (Maven), org.apache.flink:flink-runtime_2.12 (Maven). Ecosystems affected: Maven.

How do I fix GHSA-395w-qhqr-9fr6?

Update org.apache.flink:flink-runtime_2.11 to 1.11.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-395w-qhqr-9fr6 is resolved across your whole dependency graph.

How do I detect GHSA-395w-qhqr-9fr6 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.flink:flink-runtime_2.11. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-395w-qhqr-9fr6 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-395w-qhqr-9fr6?

O3 pinpoints whether GHSA-395w-qhqr-9fr6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-395w-qhqr-9fr6 actively exploited in the wild?

Yes. There are 15 known exploit references for GHSA-395w-qhqr-9fr6, including 1 documented proof-of-concept exploit on Exploit-DB and 10 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-395w-qhqr-9fr6?

GHSA-395w-qhqr-9fr6 has an EPSS (Exploit Prediction Scoring System) score of 97.9%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is GHSA-395w-qhqr-9fr6?

GHSA-395w-qhqr-9fr6 is classified as CWE-552 (CWE-552). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for GHSA-395w-qhqr-9fr6?

A Nuclei detection template exists for GHSA-395w-qhqr-9fr6, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-395w-qhqr-9fr6 published, and has it been updated?

GHSA-395w-qhqr-9fr6 was published on January 6, 2021 and was last updated on October 22, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

GHSA-395w-qhqr-9fr6

HIGH

GHSA-395w-qhqr-9fr6 is a high-severity (CVSS 7.5) CWE-552 vulnerability in org.apache.flink:flink-runtime_2.11. 15 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-395w-qhqr-9fr6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Path Traversal in Apache Flink

Also known asBIT-flink-2020-17519CVE-2020-17519

Published

Jan 6, 2021

Updated

Oct 22, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

15 known

Exploitation data as of Sep 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

CISA’s SSVC triage classifies this CVE as under active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for GHSA-395w-qhqr-9fr6.

EPSS Exploitation Probability

via FIRST.org ↗

97.9%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-395w-qhqr-9fr6 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE sits: patch-first territory.

Where this sits among everything scored

Of 0 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

2 pkgs affected

☕org.apache.flink:flink-runtime_2.11☕org.apache.flink:flink-runtime_2.12

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.flink:flink-runtime_2.11`	≥ 1.11.0&&< 1.11.3	1.11.3
☕Maven	`org.apache.flink:flink-runtime_2.12`	≥ 1.11.0&&< 1.11.3	1.11.3

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-49398webappsjava✓ Verified

Apache Flink 1.11.0 - Unauthenticated Arbitrary File Read (Metasploit)

by SunCSR Team · Jan 8, 2021

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.flink:flink-runtime_2.11. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.flink:flink-runtime_2.11 to 1.11.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-395w-qhqr-9fr6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-395w-qhqr-9fr6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-395w-qhqr-9fr6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-395w-qhqr-9fr6 in your dependencies?

O3 detects GHSA-395w-qhqr-9fr6 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works