CVE-2022-26612

CVE-2022-26612 is a critical-severity path traversal vulnerability in org.apache.hadoop:hadoop-common (maven), affecting versions >= 3.2.0, < 3.2.3. It is fixed in 3.2.3, 2.10.2, 3.3.3.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Path traversal in Hadoop

In Apache Hadoop, The unTar function uses unTarUsingJava function on Windows and the built-in tar utility on Unix and other OSes. As a result, a TAR entry may create a symlink under the expected extraction directory which points to an external directory. A subsequent TAR entry may extract an arbitrary file into the external directory using the symlink name. This however would be caught by the same targetDirPath check on Unix because of the getCanonicalPath call. However on Windows, getCanonicalPath doesn't resolve symbolic links, which bypasses the check. unpackEntries during TAR extraction follows symbolic links which allows writing outside expected base directory on Windows. This was addressed in Apache Hadoop 2.10.2, 3.2.3, 3.3.3, and 3.4.0.

Impact

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2022-26612 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.2.3, 2.10.2, 3.3.3); upgrading removes the vulnerable code path.

Affected versions

org.apache.hadoop:hadoop-common (>= 3.2.0, < 3.2.3) org.apache.hadoop:hadoop-common (< 2.10.2) org.apache.hadoop:hadoop-common (>= 3.3.0, < 3.3.3)

Security releases

org.apache.hadoop:hadoop-common → 3.2.3 (maven) org.apache.hadoop:hadoop-common → 2.10.2 (maven) org.apache.hadoop:hadoop-common → 3.3.3 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.apache.hadoop:hadoop-common to 3.2.3 or later; org.apache.hadoop:hadoop-common to 2.10.2 or later; org.apache.hadoop:hadoop-common to 3.3.3 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2022-26612? CVE-2022-26612 is a critical-severity path traversal vulnerability in org.apache.hadoop:hadoop-common (maven), affecting versions >= 3.2.0, < 3.2.3. It is fixed in 3.2.3, 2.10.2, 3.3.3. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
  2. How severe is CVE-2022-26612? CVE-2022-26612 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of org.apache.hadoop:hadoop-common are affected by CVE-2022-26612? org.apache.hadoop:hadoop-common (maven) versions >= 3.2.0, < 3.2.3 is affected.
  4. Is there a fix for CVE-2022-26612? Yes. CVE-2022-26612 is fixed in 3.2.3, 2.10.2, 3.3.3. Upgrade to this version or later.
  5. Is CVE-2022-26612 exploitable, and should I be worried? Whether CVE-2022-26612 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2022-26612 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2022-26612?
    • Upgrade org.apache.hadoop:hadoop-common to 3.2.3 or later
    • Upgrade org.apache.hadoop:hadoop-common to 2.10.2 or later
    • Upgrade org.apache.hadoop:hadoop-common to 3.3.3 or later

Other vulnerabilities in org.apache.hadoop:hadoop-common

Stop the waste.
Protect your environment with Kodem.