Apache Camel-Google-Storage: the consumer appended the remote object name to the configured downloadFileName directory without constraining the result
CVE-2026-66907GHSA-f78g-9385-qxqj
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.apache.camel:camel-google-storage 4.22.0, 4.18.4, 4.14.9), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.apache.camel:camel-google-storage
- Affected
- >= 4.0.0, < 4.14.9>= 4.15.0, < 4.18.4>= 4.19.0, < 4.22.0
- Fixed in
- 4.22.0, 4.14.9, 4.18.4
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-f78g-9385-qxqj lists affected ranges: Maven org.apache.camel:camel-google-storage >=4.0.0 =4.15.0 =4.19.0 <4.22.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-f78g-9385-qxqj lists affected ranges: Maven org.apache.camel:camel-google-storage >=4.0.0 =4.15.0 =4.19.0 <4.22.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- EPSS
- CVE-2026-66907: 0.81% estimated exploitation activity in the next 30 days; percentile 56.91 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Relative path traversal vulnerability in Apache Camel Google Storage 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-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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-f78g-9385-qxqj
- Revision 1 · created ·
Published from osv record GHSA-f78g-9385-qxqj
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-66907 Advisory: Apache Camel-Google-Storage: the consumer appended the remote object name to the configured downloadFileName directory without constraining the result IDs: CVE-2026-66907, GHSA-f78g-9385-qxqj Record: https://patchnext.com/advisories/cve-2026-66907 (revision 2, source checked 26 Oct 2026, 16:55 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: org.apache.camel:camel-google-storage 4.22.0, 4.18.4, 4.14.9. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.apache.camel:camel-google-storage: affected >= 4.0.0, < 4.14.9; >= 4.15.0, < 4.18.4; >= 4.19.0, < 4.22.0; fixed in 4.22.0, 4.14.9, 4.18.4 ## Suggested inspection (read-only) - Maven org.apache.camel:camel-google-storage: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on org.apache.camel:camel-google-storage. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-f78g-9385-qxqj (OSV record GHSA-f78g-9385-qxqj lists affected ranges: Maven org.apache.camel:camel-google-storage >=4.0.0 =4.15.0 =4.19.0 <4.22.0 (fixed)) - Verified: https://github.com/advisories/GHSA-f78g-9385-qxqj (GitHub-reviewed advisory GHSA-f78g-9385-qxqj lists affected ranges: Maven org.apache.camel:camel-google-storage >=4.0.0 =4.15.0 =4.19.0 <4.22.0) Commands are suggestions: review each one before running it.
Loading voting…