How severe is CVE-2018-11765?

CVE-2018-11765 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-11765?

CVE-2018-11765 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 CVE-2018-11765?

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 CVE-2018-11765 is resolved across your whole dependency graph.

How do I detect CVE-2018-11765 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 CVE-2018-11765 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-2018-11765 actively exploited in the wild?

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

CVE-2018-11765 has an EPSS (Exploit Prediction Scoring System) score of 5.2%, placing it in the 92th 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-2018-11765?

CVE-2018-11765 is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2018-11765 published, and has it been updated?

CVE-2018-11765 was published on September 30, 2020 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-2018-11765 — hadoop-main

HIGH

CVE-2018-11765 is a high-severity (CVSS 7.5) Improper 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.

Improper Authentication in Apache Hadoop

Also known asGHSA-rhh9-cm65-3w54

Published

Sep 30, 2020

Updated

Jul 8, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

5.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs92th percentile — riskier than 92% of all scored CVEsHighest risk

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

How urgent is this, really

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

Where this sits among everything scored

Of 385,987 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-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-alpha2 to 3.0.0, 2.9.0 to 2.9.2, 2.8.0 to 2.8.5, any users can access some servlets without authentication when Kerberos authentication is enabled and SPNEGO through HTTP is not enabled.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.hadoop:hadoop-main`	≥ 3.0.0-alpha2&&< 3.0.1	3.0.1`org.apache.hadoop:hadoop-main:3.0.1`
☕Maven	`org.apache.hadoop:hadoop-main`	≥ 2.9.0&&< 2.9.3	2.9.3`org.apache.hadoop:hadoop-main:2.9.3`
☕Maven	`org.apache.hadoop:hadoop-main`	≥ 2.8.0&&< 2.8.6	2.8.6`org.apache.hadoop:hadoop-main:2.8.6`

Affected Products

1 product · 4 configurations

Application

hadoopapache

≥ 2.9.0 && ≤ 2.9.2

1 version

3.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 3.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-11765 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 HatModerate

Workaround published by Red Hat

Users should upgrade to Apache Hadoop 2.10.0, 3.0.1 or upper. If it is not possible and affected version of Apache Hadoop is used, SPNEGO through HTTP should be enabled.

Source: Red Hat security advisory for CVE-2018-11765 (CC BY 4.0)

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-11765 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works