How severe is CVE-2018-19859?

CVE-2018-19859 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2018-19859?

CVE-2018-19859 affects the following packages: org.openrefine:main (Maven). Ecosystems affected: Maven.

How do I fix CVE-2018-19859?

Update org.openrefine:main to 3.2-beta or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-19859 is resolved across your whole dependency graph.

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

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

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

Yes. There are 1 known exploit references for CVE-2018-19859, 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-19859?

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

CVE-2018-19859 is classified as Path Traversal (CWE-22). This weakness type 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-19859 published, and has it been updated?

CVE-2018-19859 was published on December 5, 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

MEDIUM severity

CVE-2018-19859 — main

MEDIUMFix: OpenRefine/OpenRefine#1901

CVE-2018-19859 is a medium-severity (CVSS 6.5) Path Traversal vulnerability in org.openrefine:main. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.openrefine:main — see the affected versions and patch details below.

OpenRefine Directory Traversal

Also known asGHSA-f6fv-fjg8-4m6w

Published

Dec 5, 2018

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

2.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% 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.openrefine: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

OpenRefine before 3.2 beta allows directory traversal via a relative pathname in a ZIP archive.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.openrefine:main`	all versions	3.2-beta`org.openrefine:main:3.2-beta`

Affected Products

1 product · 33 configurations

Application

openrefineopenrefine

16 versions

1.01.0.11.0.21.0.31.0.51.0.61.0.71.12.02.12.52.6

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.

OpenRefine before 3.2 beta allows directory traversal via a relative pat…

github.comNVDMar 2019

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.openrefine:main, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.openrefine:main to 3.2-beta or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-19859 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

OpenRefine before 3.2 beta allows directory traversal via a relative pathname in a ZIP archive.

O3 Security · Impact-Aware SCA

Is CVE-2018-19859 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Raw vector

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

CWE Classification

CWE-22Path Traversal

Weaponization

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

OpenSSF Scorecard

Package health score

OpenRefine

5.4/10

Maintained10/10

Code-Review5/10

Branch-ProtectionN/A

Assessed Oct 26, 2026

Timeline

Disclosed

Dec 5, 2018

First exploit

Mar 28, 2019

Last updated

Oct 20, 2026

Identifiers

CVE-2018-19859

GHSA-f6fv-fjg8-4m6w

References

Advisorygithub.com Advisorynvd.nist.gov · CVE 2018 19859 Webgithub.com · e243e73e4064de87a913946bd320fbbe246da656 Packagegithub.com · OpenRefine Evidencegithub.com

Related vulnerabilities

Also affects main

This CVE is medium severity; 3 of 3 other CVEs affecting main are rated as high or higher (top: high).

CVE-2024-47879CVE-2022-41401CVE-2023-37476

Same weakness: CWE-22

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

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

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026

CVE-2018-19859 — main

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-19859 in your dependencies?