How severe is CVE-2020-9492?

CVE-2020-9492 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-9492?

CVE-2020-9492 affects the following packages: org.apache.hadoop:hadoop-common (Maven), org.apache.hadoop:hadoop-common (Maven), org.apache.hadoop:hadoop-common (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-9492?

Update org.apache.hadoop:hadoop-common to 3.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-9492 is resolved across your whole dependency graph.

How do I detect CVE-2020-9492 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.hadoop:hadoop-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2020-9492 if there is no patch (or I can't update yet)?

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.

Is CVE-2020-9492 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-9492 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 CVE-2020-9492?

CVE-2020-9492 has an EPSS (Exploit Prediction Scoring System) score of 4.4%, placing it in the 91th 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.

What type of vulnerability is CVE-2020-9492?

CVE-2020-9492 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2020-9492 published, and has it been updated?

CVE-2020-9492 was published on January 26, 2021 and was last updated on July 8, 2026. 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

CVE-2020-9492 — hadoop-common

HIGHFix: apache/hadoop@ca65409

CVE-2020-9492 is a high-severity (CVSS 8.8) CWE-863 vulnerability in org.apache.hadoop:hadoop-common. A fix is available for org.apache.hadoop:hadoop-common — see the affected versions and patch details below.

Improper Privilege Management in Apache Hadoop

Also known asBIT-solr-2020-9492GHSA-f8vc-wfc8-hxqh

Published

Jan 26, 2021

Updated

Jul 8, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

4.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2020-9492 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 386,684 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected

☕org.apache.hadoop:hadoop-common☕org.apache.hadoop:hadoop-common☕org.apache.hadoop:hadoop-common

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 3.2.0 to 3.2.1, 3.0.0-alpha1 to 3.1.3, and 2.0.0-alpha to 2.10.0, WebHDFS client might send SPNEGO authorization header to remote URL without proper verification.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.hadoop:hadoop-common`	≥ 3.2.0&&< 3.2.2	3.2.2`org.apache.hadoop:hadoop-common:3.2.2`
☕Maven	`org.apache.hadoop:hadoop-common`	≥ 3.0.0&&< 3.1.4	3.1.4`org.apache.hadoop:hadoop-common:3.1.4`
☕Maven	`org.apache.hadoop:hadoop-common`	≥ 2.0.0&&< 2.10.1	2.10.1`org.apache.hadoop:hadoop-common:2.10.1`

Affected Products

3 products · 7 configurations

Application

hadoopapache

≥ 3.2.0 && ≤ 3.2.1

range

Application

solrapache

2 versions

8.6.08.6.2

Application

financial services crime and compliance management studiooracle

2 versions

8.0.8.2.08.0.8.3.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-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.hadoop:hadoop-common to 3.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-9492 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

While OpenShift Container Platform (OCP) does package a vulnerable version of hadoop-hdfs-client in the hadoop and hive containers, the HDFS storage back-end is not enabled by default and is largely undocumented/unsupported. However, as it still can be enabled by using the configuration option…

Product	Fixed in	Advisory
RHAF Camel-K 1.8	`hadoop-hdfs-client`	RHSA-2022:6407
RHINT Camel-Q 2.7	see advisory	RHSA-2022:5606

Frequently Asked Questions

In Apache Hadoop 3.2.0 to 3.2.1, 3.0.0-alpha1 to 3.1.3, and 2.0.0-alpha to 2.10.0, WebHDFS client might send SPNEGO authorization header to remote URL without proper verification.

O3 Security · Impact-Aware SCA

Is CVE-2020-9492 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2020-9492 — hadoop-common

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2020-9492 in your dependencies?