CVE-2026-66907: Apache Camel-Google-Storage The Consumer Appended The Remote Vulnerability
HIGHCVE-2026-66907 is a HIGH (CVSS 7.5) the consumer appended the remote vulnerability (CWE-23: Relative Path Traversal) affecting Apache Camel-Google-Storage libraries in the Maven ecosystem. The issue involves the consumer appended the remote object name to the configured downloadfilename directory without constraining the result. Remediation is available by upgrading affected packages to version 4.14.9, 4.18.4, 4.22.0.
CVE-2026-66907 at a Glance
Security Impact
CVSS: 7.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).
How to Fix CVE-2026-66907
To remediate this vulnerability, upgrade all affected Apache Camel-Google-Storage dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-google-storage</artifactId>
<version>4.14.9</version>
</dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-google-storage</artifactId>
<version>4.18.4</version>
</dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-google-storage</artifactId>
<version>4.22.0</version>
</dependency>
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-66907, 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-Google-Storage 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-Google-Storage, 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
CVE-2026-66907 Affected Apache Camel-Google-Storage Versions
3 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.apache.camel:camel-google-storage
|
Maven |
≥ 4.0.0
< 4.14.9
|
4.14.9
|
|
org.apache.camel:camel-google-storage
|
Maven |
≥ 4.15.0
< 4.18.4
|
4.18.4
|
|
org.apache.camel:camel-google-storage
|
Maven |
≥ 4.19.0
< 4.22.0
|
4.22.0
|
References
Frequently Asked Questions
What is CVE-2026-66907?
Which Apache Camel-Google-Storage versions are affected?
What version fixes CVE-2026-66907?
Is camel-google-storage affected?
What is the CVSS score of CVE-2026-66907?
What CWE is associated with CVE-2026-66907?
How can I check Maven dependencies for CVE-2026-66907?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-f78g-9385-qxqj",
"modified" : "2026-08-28T21:55:10Z",
"published" : "2026-08-24T18:31:51Z",
"aliases" : [ "CVE-2026-66907" ],
"summary" : "Apache Camel-Google-Storage: the consumer appended the remote object name to the configured downloadFileName directory without constraining the result",
"details" : "Relative path traversal vulnerability in Apache Camel Google Storage 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-google-storage consumer downloads Google Cloud Storage objects to the local filesystem when the downloadFileName option is set. That option is documented as a folder or a filename, and when its value contains no expression token the consumer builds the local destination by appending the object name to it: evaluateFileExpression sets the Exchange file-name header to the remote object name and evaluates downloadFileName + \"/${file:name}\". The ${file:name} token returns the file-name header verbatim, unlike ${file:onlyname}, which applies FileUtil.stripPath to it. The resulting string was passed directly to new File(result) and blob.downloadTo(file.toPath()) with no lexical normalization and no check that the destination stayed inside the configured directory. The object name is not route-controlled data: the consumer lists the bucket, iterates every returned blob and creates one exchange per object from blob.getBlobId().getName() verbatim, and the filter option that could restrict those names is not applied at all unless it has been explicitly set. Google Cloud Storage object names are opaque UTF-8 keys that the service stores and lists exactly as written, with no server-side canonicalization, and a forward slash is only a display convention for pseudo-directories, so a key containing parent-directory segments survives round-tripping intact. An object name containing such segments therefore resolved to a location outside the configured downloadFileName directory, letting anyone able to influence the names present in the consumed bucket 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 downloadFileName option is an ordinary consumer parameter and carries no security marker, so nothing signalled to users that its value was not being enforced as a containment boundary. The defect is consumer-only; the producer has no download-to-file sink. Camel's other file-download consumers - camel-file, camel-ftp, camel-smb, camel-mina-sftp, camel-azure-files and the Azure Storage download paths - already constrained their local downloads to the configured directory using a path-segment boundary check; camel-google-storage was the remaining object-store download sink 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, set the filter option to a regular expression that accepts only simple single-segment object names, so that any name carrying a path separator or a parent-directory segment is excluded before an exchange is created; note that no filtering whatsoever is applied when the option is left unset, and that the expression is matched against the whole object name. Alternatively, give downloadFileName an explicit expression that does not carry the remote path through, for example one built on ${file:onlyname} rather than the implicit ${file:name}, keeping in mind that a downloadFileName containing an expression is treated as route-author-controlled and is not covered by the containment check added in the fix. As defence in depth, treat the object names in any externally writable bucket as untrusted input and do not derive local filesystem paths from them.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "org.apache.camel:camel-google-storage"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "4.0.0"
}, {
"fixed" : "4.14.9"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.apache.camel:camel-google-storage"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "4.15.0"
}, {
"fixed" : "4.18.4"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.apache.camel:camel-google-storage"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "4.19.0"
}, {
"fixed" : "4.22.0"
} ]
} ]
} ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-66907"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/pull/25179"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/pull/25180"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/pull/25181"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/pull/25182"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/commit/277ab7b7af9bd3beb789d458d54b00b704647191"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/commit/4b9b4ade15148e1512b39f302075b36c7a092e86"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/commit/a6f73c6d2828fe2b76bf423bad92f98d80af7437"
}, {
"type" : "WEB",
"url" : "https://camel.apache.org/security/CVE-2026-66907.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-24279"
}, {
"type" : "WEB",
"url" : "http://www.openwall.com/lists/oss-security/2026/08/24/11"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-23" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-08-28T21:55:10Z",
"nvd_published_at" : "2026-08-24T17:18:06Z"
}
}