Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-66907 high CVSS 7.5

Vulnerability in org.apache.camel:camel-google-storage (CVE-2026-66907)

Summary

Vulnerability in org.apache.camel:camel-google-storage (CVE-2026-66907). Confidential information can be exposed externally. Mitigation: upgrade to 4.22.0 or later.

Original description

The description as published by the source.

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 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 co…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-66907 has been found in org.apache.camel:camel-google-storage.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade org.apache.camel:camel-google-storage to 4.22.0 or later.
If unsure, ask your IT team or search "org.apache.camel:camel-google-storage CVE-2026-66907" on the vendor's site.

CVE-2026-66907 (org.apache.camel:camel-google-storage) — CWE-23 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 4.22.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-23) exists in org.apache.camel:camel-google-storage.

📍 Affected scope

Check the vendor advisory for the affected versions of org.apache.camel:camel-google-storage.

🔥 Severity

Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 4.22.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.apache.camel:camel-google-storage を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.apache.camel:camel-google-storage to 4.22.0

    ステージング環境で 4.22.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.apache.camel:camel-google-storage
[{"type":"ECOSYSTEM","events":[{"introduced":"4.19.0"},{"fixed":"4.22.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details