NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

Apache Camel's Mail is vulnerable to path traversalGHSA-jv74-f9pj-xp3f

MEDIUMFix: apache/camel@4580e4d

GHSA-jv74-f9pj-xp3f 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.

Also known asCVE-2018-8041
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 10, 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
0.26%4.19%8.13%12.1%2.5%9.6%May 26Sep 26Nov 26

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
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.camel:camel-mail≥ 2.20.0&&< 2.20.42.20.4org.apache.camel:camel-mail:2.20.4
☕Mavenorg.apache.camel:camel-mail≥ 2.21.0&&< 2.21.22.21.2org.apache.camel:camel-mail:2.21.2
☕Mavenorg.apache.camel:camel-mail≥ 2.22.0&&< 2.22.12.22.1org.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

  1. 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.

  2. 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 GHSA-jv74-f9pj-xp3f is resolved across your whole dependency graph.

  3. 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
ProductFixed inAdvisory
Red Hat Fuse 7.2camel-mailRHSA-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 GHSA-jv74-f9pj-xp3f in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Apache Camel's Mail is vulnerable to path traversal