A relative path traversal issue exists in the `camel-azure-storage-datalake` component during the `downloadToFile` operation. The component writes files to a local directory specified by the `fileDir` endpoint option by joining it with the remote path name provided by the Azure SDK without lexical normalization or boundary checks. Because the `DataLakeConsumer.createBatchExchangesFromPath` function creates exchanges from `PathItem.getName()` verbatim, a remote file name containing parent-directory segments can resolve to a location outside the intended `fileDir`. This allows an attacker who can influence file names in the consumed Data Lake filesystem to create or overwrite files on the local filesystem with the privileges of the Camel process, potentially leading to a loss of file integrity or further privilege escalation.