As cited
Copy frozen at (site build).
vulnerabilities
CVE-2026-103412: Apache Camel Karavan: project file name path traversal when committing a project to Git
A path traversal vulnerability in Apache Camel Karavan versions 3.18.0 before 4.22.1 allows authenticated users to write files outside the intended directory when committing a project to Git. The vulnerability stems from improper validation of project file names supplied through the project file application programming interface (API), which are used verbatim as path segments in the working copy.
Why it matters: Developers and operators using affected Camel Karavan versions face risk of arbitrary file writes on systems running the application; update to version 4.22.1 or later immediately.
- Source published
- First seen by Cybersecurity Tracker
Source attribution
Correction
Correction recorded as of .
vulnerabilities
CVE-2026-103412: Apache Camel Karavan: project file name path traversal when committing a project to Git
No summary had been written when this copy was frozen.
- First seen by Cybersecurity Tracker
Source attribution
Correction
Correction recorded as of .
vulnerabilities
CVE-2026-103412: Apache Camel Karavan: project file name path traversal when committing a project to Git
Apache Camel Karavan versions 3.18.0 before 4.22.1 contain a path traversal vulnerability in the project file application programming interface (API). An attacker with login credentials could supply a malicious project file name that bypasses directory restrictions when the project is committed to Git, potentially leading to unauthorized file access or modification.
Why it matters: Organizations running vulnerable Camel Karavan instances should patch immediately, as authenticated attackers can exploit the API to traverse directories and compromise file integrity.
- Source published
- First seen by Cybersecurity Tracker