Authentication bypass in Apache HadoopGHSA-4fh8-pm7g-pmxq
HIGHGHSA-4fh8-pm7g-pmxq is a high-severity (CVSS 8.8) Missing Authentication vulnerability in org.apache.hadoop:hadoop-main. A fix is available for org.apache.hadoop:hadoop-main — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-4fh8-pm7g-pmxq by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.apache.hadoop:hadoop-main☕org.apache.hadoop:hadoop-main☕org.apache.hadoop:hadoop-mainReal-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
Web endpoint authentication check is broken in Apache Hadoop 3.0.0-alpha4, 3.0.0-beta1, and 3.0.0. Authenticated users may impersonate any user even if no proxy user is configured.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.hadoop:hadoop-main | ≥ 3.0.0-alpha4&&< 3.0.1 | 3.0.1org.apache.hadoop:hadoop-main:3.0.1 |
| ☕Maven | org.apache.hadoop:hadoop-main | ≥ 3.0.0-beta1&&< 3.0.1 | 3.0.1org.apache.hadoop:hadoop-main:3.0.1 |
| ☕Maven | org.apache.hadoop:hadoop-main | ≥ 3.0.0&&< 3.0.1 | 3.0.1org.apache.hadoop:hadoop-main:3.0.1 |
Affected Products
hadoopapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.hadoop:hadoop-main, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.hadoop:hadoop-main to 3.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4fh8-pm7g-pmxq is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is GHSA-4fh8-pm7g-pmxq in your dependencies?
Find it across Maven, including transitive dependencies.