How severe is GHSA-37pw-qw47-4jxm?

GHSA-37pw-qw47-4jxm has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-37pw-qw47-4jxm?

GHSA-37pw-qw47-4jxm affects the following packages: org.apache.hadoop:hadoop-main (Maven), org.apache.hadoop:hadoop-main (Maven), org.apache.hadoop:hadoop-main (Maven). Ecosystems affected: Maven.

How do I fix GHSA-37pw-qw47-4jxm?

Update org.apache.hadoop:hadoop-main to 2.8.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-37pw-qw47-4jxm is resolved across your whole dependency graph.

How do I detect GHSA-37pw-qw47-4jxm in my Maven dependencies?

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.

How do I mitigate GHSA-37pw-qw47-4jxm 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.

Is GHSA-37pw-qw47-4jxm actively exploited in the wild?

No public exploit code has been indexed for GHSA-37pw-qw47-4jxm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-37pw-qw47-4jxm?

GHSA-37pw-qw47-4jxm has an EPSS (Exploit Prediction Scoring System) score of 3.9%, placing it in the 90th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-37pw-qw47-4jxm published, and has it been updated?

GHSA-37pw-qw47-4jxm was published on May 31, 2019 and was last updated on February 16, 2024. 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

Privilege escalation vulnerability in Apache HadoopGHSA-37pw-qw47-4jxm

HIGH

GHSA-37pw-qw47-4jxm is a high-severity (CVSS 8.8) 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.

Also known asCVE-2018-8029

Published

May 31, 2019

Updated

Feb 16, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

3.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

☕org.apache.hadoop:hadoop-main☕org.apache.hadoop:hadoop-main☕org.apache.hadoop:hadoop-main

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

In Apache Hadoop versions 3.0.0-alpha1 to 3.1.0, 2.9.0 to 2.9.1, and 2.2.0 to 2.8.4, a user who can escalate to yarn user can possibly run arbitrary commands as root user.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.hadoop:hadoop-main`	≥ 2.2.0&&< 2.8.4	2.8.4`org.apache.hadoop:hadoop-main:2.8.4`
☕Maven	`org.apache.hadoop:hadoop-main`	≥ 2.9.0&&< 2.9.2	2.9.2`org.apache.hadoop:hadoop-main:2.9.2`
☕Maven	`org.apache.hadoop:hadoop-main`	≥ 3.0.0&&< 3.1.1	3.1.1`org.apache.hadoop:hadoop-main:3.1.1`

Affected Products

1 product · 10 configurations

Application

hadoopapache

≥ 3.0.1 && ≤ 3.1.0

3 versions

2.9.02.9.13.0.0

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.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 2.8.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-37pw-qw47-4jxm 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.

Frequently Asked Questions

In Apache Hadoop versions 3.0.0-alpha1 to 3.1.0, 2.9.0 to 2.9.1, and 2.2.0 to 2.8.4, a user who can escalate to yarn user can possibly run arbitrary commands as root user.

O3 Security · Impact-Aware SCA

Is GHSA-37pw-qw47-4jxm in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works