How severe is CVE-2019-0194?

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

Which packages are affected by CVE-2019-0194?

CVE-2019-0194 affects the following packages: org.apache.camel:camel-core (Maven), org.apache.camel:camel-core (Maven), org.apache.camel:camel-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-0194?

Update org.apache.camel:camel-core to 2.21.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-0194 is resolved across your whole dependency graph.

How do I detect CVE-2019-0194 in my Maven dependencies?

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

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

Yes. There are 5 known exploit references for CVE-2019-0194, including 5 in-the-wild exploitations 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-2019-0194?

CVE-2019-0194 has an EPSS (Exploit Prediction Scoring System) score of 8.5%, placing it in the 95th 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-2019-0194?

CVE-2019-0194 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-2019-0194 published, and has it been updated?

CVE-2019-0194 was published on April 30, 2019 and was last updated on October 24, 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-2019-0194 — camel-core

HIGHFix: apache/camel#2700

CVE-2019-0194 is a high-severity (CVSS 7.5) Path Traversal vulnerability in org.apache.camel:camel-core. 5 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.apache.camel:camel-core — see the affected versions and patch details below.

Path Traversal in Apache Camel

Also known asGHSA-4wjq-69rc-8wcp

Published

Apr 30, 2019

Updated

Oct 24, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

5 known

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

EPSS Exploitation Probability

via FIRST.org ↗

8.5%probability of exploitation in next 30 days

Lower Risk0.00%

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

3 pkgs affected

☕org.apache.camel:camel-core☕org.apache.camel:camel-core☕org.apache.camel:camel-core

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

Apache Camel's File is vulnerable to directory traversal. Camel 2.21.0 to 2.21.3, 2.22.0 to 2.22.2, 2.23.0 and the unsupported Camel 2.x (2.19 and earlier) versions may be also affected.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.camel:camel-core`	≥ 2.21.0&&< 2.21.5	2.21.5`org.apache.camel:camel-core:2.21.5`
☕Maven	`org.apache.camel:camel-core`	≥ 2.22.0&&< 2.22.3	2.22.3`org.apache.camel:camel-core:2.22.3`
☕Maven	`org.apache.camel:camel-core`	≥ 2.23.0&&< 2.23.1	2.23.1`org.apache.camel:camel-core:2.23.1`

Affected Products

1 product · 4 configurations

Application

camelapache

≥ 2.22.0 && ≤ 2.22.2

1 version

2.23.0

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.

Apache Camel's File is vulnerable to directory traversal. Camel 2.21.0 t…

lists.apache.orgNVDMay 2019

Report on lists.apache.org

lists.apache.orgNVDMay 2019

Report on lists.apache.org

lists.apache.orgNVDMay 2019

Report on lists.apache.org

lists.apache.orgNVDMay 2019

Report on openwall.com

openwall.comNVDMay 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.apache.camel:camel-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.camel:camel-core to 2.21.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-0194 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.

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

RHSA-2019:0910Red Hat Fuse 7.3

Frequently Asked Questions

Apache Camel's File is vulnerable to directory traversal. Camel 2.21.0 to 2.21.3, 2.22.0 to 2.22.2, 2.23.0 and the unsupported Camel 2.x (2.19 and earlier) versions may be also affected.

O3 Security · Impact-Aware SCA

Is CVE-2019-0194 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2019-0194 — camel-core

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