How severe is CVE-2018-12036?

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

Which packages are affected by CVE-2018-12036?

CVE-2018-12036 affects the following packages: org.owasp:dependency-check-maven (Maven). Ecosystems affected: Maven.

How do I fix CVE-2018-12036?

Update org.owasp:dependency-check-maven to 3.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-12036 is resolved across your whole dependency graph.

How do I detect CVE-2018-12036 in my Maven dependencies?

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

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

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2018-12036 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2018-12036, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-12036?

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

CVE-2018-12036 is classified as Path Traversal (CWE-22), CWE-123 (CWE-123). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

CVE-2018-12036 was published on June 7, 2018 and was last updated on October 20, 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-12036 — dependency-check-maven

HIGH

CVE-2018-12036 is a high-severity (CVSS 7.8) Path Traversal vulnerability in org.owasp:dependency-check-maven. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.owasp:dependency-check-maven — see the affected versions and patch details below.

Path Traversal in OWASP Dependency-Check

Also known asGHSA-hcwx-7q5v-vc67

Published

Jun 7, 2018

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs77th percentile — riskier than 77% 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

1 pkg affected

☕org.owasp:dependency-check-maven

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

OWASP Dependency-Check before 3.2.0 allows attackers to write to arbitrary files via a crafted archive that holds directory traversal filenames.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.owasp:dependency-check-maven`	all versions	3.2.0`org.owasp:dependency-check-maven:3.2.0`

Affected Products

1 product · 1 configurations

Application

dependency-checkowasp

< 3.2.0

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

OWASP Dependency-Check before 3.2.0 allows attackers to write to arbitra…

github.comNVDJul 2018

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.owasp:dependency-check-maven, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.owasp:dependency-check-maven to 3.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-12036 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

OWASP Dependency-Check before 3.2.0 allows attackers to write to arbitrary files via a crafted archive that holds directory traversal filenames.

O3 Security · Impact-Aware SCA

Is CVE-2018-12036 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.8/10CVSS v3 base

Vector breakdown

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CWE Classification

CWE-22Path Traversal CWE-123CWE-123

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

OpenSSF Scorecard

Package health score

DependencyCheck

4.7/10

Maintained0/10

Code-Review0/10

Branch-Protection0/10

Assessed Oct 19, 2026

Timeline

Disclosed

Jun 7, 2018

First exploit

Jul 27, 2018

Last updated

Oct 20, 2026

Identifiers

CVE-2018-12036

GHSA-hcwx-7q5v-vc67

References

Advisorygithub.com · RELEASE NOTES.md Advisorynvd.nist.gov · CVE 2018 12036 Packagegithub.com · DependencyCheck Evidencegithub.com · zip slip vulnerability

Related vulnerabilities

Also affects dependency-check-maven

This CVE is high severity — higher than any of the other 2 CVEs affecting dependency-check-maven (highest there: moderate).

CVE-2024-23686GHSA-qqhq-8r2c-c3f5

Same weakness: CWE-22

This CVE is high severity; 3 of 6 other CVEs with CWE-22 are rated as high or higher (top: critical).

CVE-2026-62331GHSA-4xm8-rg9h-jhq2CVE-2026-9083CVE-2026-115908CVE-2026-118667CVE-2026-118654Browse all CWE-22

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026

CVE-2018-12036 — dependency-check-maven

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

Frequently Asked Questions

Is CVE-2018-12036 in your dependencies?