CVE-2026-60093: Apache Camel-Azure-Storage-DataLake The DownloadToFile Operation Built The Vulnerability

MODERATE
Advisory Identifier: GHSA-7jwc-q3fj-c9pq
CVSS 5.5
CWE-23
Published
Advisory Summary

CVE-2026-60093 is a MODERATE (CVSS 5.5) the downloadtofile operation built the vulnerability (CWE-23: Relative Path Traversal) affecting Apache Camel-Azure-Storage-DataLake libraries in the Maven ecosystem. The issue involves the downloadtofile operation built the local download target from the remote path name without constraining it to the configured filedir. Remediation is available by upgrading affected packages to version 4.14.9, 4.18.4, 4.22.0.

CVE-2026-60093 at a Glance

CVE Identifier CVE-2026-60093
GHSA Identifier GHSA-7jwc-q3fj-c9pq
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification CWE-23: Relative Path Traversal
Affected Product Apache Camel-Azure-Storage-DataLake
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-60093

To remediate this vulnerability, upgrade all affected Apache Camel-Azure-Storage-DataLake dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.apache.camel:camel-azure-storage-datalake fixed: 4.14.9
<dependency>
    <groupId>org.apache.camel</groupId>
    <artifactId>camel-azure-storage-datalake</artifactId>
    <version>4.14.9</version>
</dependency>
org.apache.camel:camel-azure-storage-datalake fixed: 4.18.4
<dependency>
    <groupId>org.apache.camel</groupId>
    <artifactId>camel-azure-storage-datalake</artifactId>
    <version>4.18.4</version>
</dependency>
org.apache.camel:camel-azure-storage-datalake fixed: 4.22.0
<dependency>
    <groupId>org.apache.camel</groupId>
    <artifactId>camel-azure-storage-datalake</artifactId>
    <version>4.22.0</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=org.apache.camel

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-60093, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.apache.camel

Analyze the terminal output to locate any version of Apache Camel-Azure-Storage-DataLake in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.14.9), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.apache.camel command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-23: Relative Path Traversal, where the product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that directory. In Apache Camel-Azure-Storage-DataLake, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

CVE-2026-60093 Affected Apache Camel-Azure-Storage-DataLake Versions

3 component(s)
Fixed Versions:
4.14.94.18.44.22.0
Product / Package Ecosystem Affected Versions Fixed Version
org.apache.camel:camel-azure-storage-datalake
Maven
≥ 4.0.0
< 4.14.9
4.14.9
org.apache.camel:camel-azure-storage-datalake
Maven
≥ 4.15.0
< 4.18.4
4.18.4
org.apache.camel:camel-azure-storage-datalake
Maven
≥ 4.19.0
< 4.22.0
4.22.0

References

NVD — CVE-2026-60093 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-60093
Apache Camel-Azure-Storage-DataLake Source Repository REPOSITORY
https://github.com/apache/camel/pull/24542
Apache Camel-Azure-Storage-DataLake Source Repository REPOSITORY
https://github.com/apache/camel/pull/24581
Apache Camel-Azure-Storage-DataLake Source Repository REPOSITORY
https://github.com/apache/camel/pull/24582
Apache Camel-Azure-Storage-DataLake Source Repository REPOSITORY
https://github.com/apache/camel/pull/24585
Security Fix Commit FIX COMMIT
https://github.com/apache/camel/commit/007929bb732a8c5e3e49d4d3c6c8adc2aab13340
Security Fix Commit FIX COMMIT
https://github.com/apache/camel/commit/55fcbaf8bc1936cae90abdea5adecbc43e57340e
Security Fix Commit FIX COMMIT
https://github.com/apache/camel/commit/857d0cd3024b706ce80f3d2a4aa111e5e94a3e59
Apache Camel-Azure-Storage-DataLake Security Information SECURITY
https://camel.apache.org/security/CVE-2026-60093.html
Apache Camel-Azure-Storage-DataLake Source Repository REPOSITORY
https://github.com/apache/camel
Apache Camel-Azure-Storage-DataLake Release RELEASE
https://github.com/apache/camel/releases/tag/camel-4.14.9
Apache Camel-Azure-Storage-DataLake Release RELEASE
https://github.com/apache/camel/releases/tag/camel-4.18.4
Apache Camel-Azure-Storage-DataLake Release RELEASE
https://github.com/apache/camel/releases/tag/camel-4.22.0
issues.apache.org/jira/browse/camel-2... WEB
https://issues.apache.org/jira/browse/CAMEL-23942
Apache Camel-Azure-Storage-DataLake Security Information SECURITY
http://www.openwall.com/lists/oss-security/2026/08/24/8

Frequently Asked Questions

What is CVE-2026-60093?
CVE-2026-60093 is a security vulnerability in Apache Camel-Azure-Storage-DataLake involving the downloadToFile operation built the local download target from the remote path name without constraining it to the configured fileDir under CWE-23: Relative Path Traversal.
Which Apache Camel-Azure-Storage-DataLake versions are affected?
Affected versions include releases prior to 4.14.9, 4.18.4, 4.22.0 across affected packages: org.apache.camel:camel-azure-storage-datalake.
What version fixes CVE-2026-60093?
Upgrading to 4.14.9, 4.18.4, 4.22.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is camel-azure-storage-datalake affected?
Yes, org.apache.camel:camel-azure-storage-datalake is affected in releases prior to 4.14.9, 4.18.4, 4.22.0. Upgrade your dependency to 4.14.9, 4.18.4, 4.22.0 or later.
What is the CVSS score of CVE-2026-60093?
CVE-2026-60093 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-60093?
CVE-2026-60093 is classified under CWE-23: Relative Path Traversal (The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that directory.).
How can I check Maven dependencies for CVE-2026-60093?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.apache.camel'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-7jwc-q3fj-c9pq",
  "modified" : "2026-08-28T20:29:23Z",
  "published" : "2026-08-24T18:31:51Z",
  "aliases" : [ "CVE-2026-60093" ],
  "summary" : "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",
  "details" : "Relative path traversal vulnerability in Apache Camel Azure-Storage Datalake component\n\nThis 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.\n\nThe 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.\n\nUsers 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.apache.camel:camel-azure-storage-datalake"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.0.0"
      }, {
        "fixed" : "4.14.9"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.apache.camel:camel-azure-storage-datalake"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.15.0"
      }, {
        "fixed" : "4.18.4"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.apache.camel:camel-azure-storage-datalake"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.19.0"
      }, {
        "fixed" : "4.22.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-60093"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/camel/pull/24542"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/camel/pull/24581"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/camel/pull/24582"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/camel/pull/24585"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/camel/commit/007929bb732a8c5e3e49d4d3c6c8adc2aab13340"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/camel/commit/55fcbaf8bc1936cae90abdea5adecbc43e57340e"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/camel/commit/857d0cd3024b706ce80f3d2a4aa111e5e94a3e59"
  }, {
    "type" : "WEB",
    "url" : "https://camel.apache.org/security/CVE-2026-60093.html"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/apache/camel"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/camel/releases/tag/camel-4.14.9"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/camel/releases/tag/camel-4.18.4"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/camel/releases/tag/camel-4.22.0"
  }, {
    "type" : "WEB",
    "url" : "https://issues.apache.org/jira/browse/CAMEL-23942"
  }, {
    "type" : "WEB",
    "url" : "http://www.openwall.com/lists/oss-security/2026/08/24/8"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-23" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-28T20:29:22Z",
    "nvd_published_at" : "2026-08-24T17:17:29Z"
  }
}