CVE-2026-60093: Apache Camel: Camel-Azure-Storage-DataLake: the downloadToFile operation built the local download target from the remote path name without constraining it to the configured fileDir
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache Camel (camel-azure-storage-datalake)to a version that resolves this vulnerability.Fixed in 4.14.9 - Upgrade
Upgrade
Apache Camel (camel-azure-storage-datalake)to a version that resolves this vulnerability.Fixed in 4.18.4 - Upgrade
Upgrade
Apache Camel (camel-azure-storage-datalake)to a version that resolves this vulnerability.Fixed in 4.22.0 - Configuration
For deployments that cannot upgrade immediately, use the endpoint regex option to filter the listed remote path names as full-string matches so that only single-segment object names are accepted; filter out any name carrying a path separator or a parent-directory segment before exchanges are created.
Apache Camel camel-azure-storage-datalake regex endpoint option = only simple single-segment names (reject any name containing a path separator or a parent-directory segment) - Compensating control
As defence in depth, treat object names from any externally writable Azure Data Lake filesystem as untrusted input and avoid deriving local filesystem paths from those object names. Where possible, avoid the downloadToFile operation on untrusted filesystems and write the payload using a local file name controlled by the route rather than one taken from the remote listing.
Event History
Frequently Asked Questions
Which Apache Camel releases are affected?
Affected releases are 4.0.0 through 4.14.8, 4.15.0 through 4.18.3, and 4.19.0 through 4.21.x. The fixed releases identified are 4.14.9, 4.18.4, and 4.22.0.
What access does an attacker need to exploit this issue?
An attacker needs to be able to influence file or path names present in the Azure Data Lake Storage Gen2 filesystem that the Camel consumer enumerates. The vulnerable consumer uses those names verbatim when creating exchanges.
Are default consumer settings affected?
Yes. The consumer applies no name filtering by default when listing paths, so a path name containing parent-directory segments can be used without relying on a custom permissive name-filter configuration.
How can I identify potentially exposed routes?
Review routes using the camel-azure-storage-datalake component that consume enumerated Data Lake paths and use the downloadToFile operation with a fileDir endpoint option. On affected versions, those routes can construct local download targets outside the configured fileDir from remote path names.