CVE-2026-103412 Apache Camel Karavan: project file name path traversal when committing a project to Git
An authenticated user can exploit path traversal in project file names to write files outside the project directory, potentially leading to code execution.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-103412?
CVE-2026-103412 is a high-severity path traversal vulnerability in Apache Camel Karavan, published on 9 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Apache Camel Karavan.
A project file name supplied through the project file API was used verbatim as a path segment when the project was written to the working copy for a Git commit, so a name containing `../` sequences caused the file content to be written outside the project directory, to any location writable by the Karavan process. An authenticated user of any role could use this to overwrite application configuration or files on the application classpath and so execute code in the Karavan container.
This issue affects Apache Camel Karavan: from 3.18.0 before 4.22.1.
Users are recommended to upgrade to version 4.22.1, which fixes the issue.
Weakness: CWE-22
Which versions are affected by CVE-2026-103412?
How do I fix CVE-2026-103412?
No fix has been published for CVE-2026-103412 yet. Limit exposure of the affected software until one is available.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-103412 being exploited?
There is no known exploitation of CVE-2026-103412 in the wild and no public exploit code.
Sources
Also known as GHSA-8cgr-63w4-hm5f.