How severe is CVE-2018-8041?

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

Which packages are affected by CVE-2018-8041?

CVE-2018-8041 affects the following packages: org.apache.camel:camel-mail (Maven), org.apache.camel:camel-mail (Maven), org.apache.camel:camel-mail (Maven). Ecosystems affected: Maven.

How do I fix CVE-2018-8041?

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

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

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

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

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

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

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

CVE-2018-8041 was published on September 17, 2018 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

MEDIUM severity

CVE-2018-8041 — camel-mail

MEDIUMFix: apache/camel@4580e4d

CVE-2018-8041 is a medium-severity (CVSS 5.3) Path Traversal vulnerability in org.apache.camel:camel-mail. A fix is available for org.apache.camel:camel-mail — see the affected versions and patch details below.

Apache Camel's Mail is vulnerable to path traversal

Also known asGHSA-jv74-f9pj-xp3f

Published

Sep 17, 2018

Updated

Oct 24, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

9.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs96th percentile — riskier than 96% 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-mail☕org.apache.camel:camel-mail☕org.apache.camel:camel-mail

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 Mail 2.20.0 through 2.20.3, 2.21.0 through 2.21.1 and 2.22.0 is vulnerable to path traversal.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.camel:camel-mail`	≥ 2.20.0&&< 2.20.4	2.20.4`org.apache.camel:camel-mail:2.20.4`
☕Maven	`org.apache.camel:camel-mail`	≥ 2.21.0&&< 2.21.2	2.21.2`org.apache.camel:camel-mail:2.21.2`
☕Maven	`org.apache.camel:camel-mail`	≥ 2.22.0&&< 2.22.1	2.22.1`org.apache.camel:camel-mail:2.22.1`

Affected Products

1 product · 3 configurations

Application

camelapache

≥ 2.21.0 && ≤ 2.21.1

1 version

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

Product	Fixed in	Advisory
Red Hat Fuse 7.2	`camel-mail`	RHSA-2018:3768

Frequently Asked Questions

Apache Camel's Mail 2.20.0 through 2.20.3, 2.21.0 through 2.21.1 and 2.22.0 is vulnerable to path traversal.

O3 Security · Impact-Aware SCA

Is CVE-2018-8041 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works