# CVE-2026-60093: Apache Camel-Azure-Storage-DataLake: the downloadToFile operation built the local download target from the remote path name without constraining it to the configured fileDir > Attackers can write files outside the configured directory via path traversal in Azure Data Lake downloads, potentially escalating privileges. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 24 Aug 2026 - **Updated:** 25 Aug 2026 - **Also known as:** GHSA-7jwc-q3fj-c9pq ## What is CVE-2026-60093? CVE-2026-60093 is a medium-severity path traversal vulnerability in Apache Camel, published on 24 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Relative path traversal vulnerability in Apache Camel Azure-Storage Datalake component This issue affects Apache Camel: from 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0. The camel-azure-storage-datalake component can download an Azure Data Lake Storage Gen2 file to the local filesystem through its downloadToFile operation, writing into the directory named by the fileDir endpoint option. DataLakeFileOperations.downloadToFile built the local target by joining fileDir with the remote path name exactly as the Azure SDK reported it (new File(fileDir, fileClientWrapper.getFileName())) and passed the result straight to the SDK download call, with no lexical normalization and no check that the resolved location stayed inside fileDir. The remote name is not route-controlled data: the consumer enumerates the filesystem in DataLakeConsumer.createBatchExchangesFromPath, which lists paths and creates one exchange per entry from PathItem.getName() verbatim, applying no name filtering by default. A path name containing parent-directory segments therefore resolved to a location outside the configured fileDir, letting anyone able to influence the names present in the consumed Data Lake filesystem cause Camel to create or overwrite a file at a location of their choosing, with the privileges of the Camel process. Depending on what the process can write to, overwriting a file outside the download directory can escalate beyond the loss of integrity of that file. The fileDir option is an ordinary common-group configuration parameter and carries no security marker, so nothing signalled to users that its value was not being enforced as a containment boundary. Camel's other file-download consumers - camel-file, camel-ftp, camel-smb, camel-mina-sftp and camel-azure-files - already constrained their local downloads to the configured directory using a path-segment boundary check; the camel-azure-storage-datalake download path was not covered by that work. Users are recommended to upgrade to version 4.22.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.9. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.4. For deployments that cannot upgrade immediately, constrain the names the consumer will act on using the regex endpoint option, which is applied to each listed path name as a full-string match, so that only simple single-segment names are accepted and any name carrying a path separator or a parent-directory segment is filtered out before an exchange is created. Alternatively, avoid the downloadToFile operation on untrusted filesystems and write the payload from the route under a file name the route itself controls, rather than one taken from the remote listing. As defence in depth, treat the object names in any externally writable Data Lake filesystem as untrusted input and do not derive local filesystem paths from them. Weakness: CWE-23 (Relative Path Traversal) ## Which versions are affected by CVE-2026-60093? 6 open source packages ship an affected version, including org.apache.camel:camel-azure-storage-datalake. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.camel:camel-azure-storage-datalake` | Maven | From 4.0.0 | 4.14.9 | | `org.apache.camel:camel-azure-storage-datalake` | Maven | From 4.0.0 | 4.14.9 | | `org.apache.camel:camel-azure-storage-datalake` | Maven | From 4.15.0 | 4.18.4 | | `org.apache.camel:camel-azure-storage-datalake` | Maven | From 4.15.0 | 4.18.4 | | `org.apache.camel:camel-azure-storage-datalake` | Maven | From 4.19.0 | 4.22.0 | | `org.apache.camel:camel-azure-storage-datalake` | Maven | From 4.19.0 | 4.22.0 | Products: Apache Camel. ## How do I fix CVE-2026-60093? Upgrade org.apache.camel:camel-azure-storage-datalake to a fixed version for your release line: 4.14.9, 4.18.4 or 4.22.0. ## Is CVE-2026-60093 being exploited? There is no known exploitation of CVE-2026-60093 in the wild and no public exploit code. Public exploit code: - Reproducer for CVE-2026-60093 (Apache Camel camel-azure-storage-datalake downloadToFile path traversal) — Camel Spring Boot + Camel Quarkus (github_poc): https://github.com/oscerd/CVE-2026-60093 ## Other vulnerabilities in Apache Camel - [CVE-2026-33453](https://insights.sbomify.com/CVE-2026-33453/): Apache camel-coap allows header injection that can lead to remote code execution (critical 10.0) - [CVE-2026-40453](https://insights.sbomify.com/CVE-2026-40453/): Apache Camel has an incomplete fix for CVE-2025-27636 (critical 9.9) - [CVE-2026-80351](https://insights.sbomify.com/CVE-2026-80351/): Apache Camel K: Camel K Tenant repositories reach Maven execution inside operator pod (critical 9.8) - [CVE-2026-80352](https://insights.sbomify.com/CVE-2026-80352/): Apache Camel K: Camel K Master trait serviceAccountName YAML injection lets CR author apply arbitrary objects (critical 9.8) - [CVE-2026-71300](https://insights.sbomify.com/CVE-2026-71300/): Apache Camel: Camel-Atmosphere-Websocket: WebSocket dispatch header injection (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-60093 and fix it if it is affected. What it is: CVE-2026-60093 is a medium-severity path traversal vulnerability in Apache Camel, published on 24 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-60093 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.camel:camel-azure-storage-datalake (Maven): affected from 4.0.0; fixed in 4.14.9 - org.apache.camel:camel-azure-storage-datalake (Maven): affected from 4.0.0; fixed in 4.14.9 - org.apache.camel:camel-azure-storage-datalake (Maven): affected from 4.15.0; fixed in 4.18.4 - org.apache.camel:camel-azure-storage-datalake (Maven): affected from 4.15.0; fixed in 4.18.4 - org.apache.camel:camel-azure-storage-datalake (Maven): affected from 4.19.0; fixed in 4.22.0 - org.apache.camel:camel-azure-storage-datalake (Maven): affected from 4.19.0; fixed in 4.22.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-60093/ (Markdown: https://insights.sbomify.com/CVE-2026-60093/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-60093 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-60093 - OSV: https://osv.dev/vulnerability/CVE-2026-60093 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-60093/ Summaries are generated and may contain mistakes; the official description above is the record.