PoC Monitor
← All CVEs
CVE-2026-66906published 24 Aug 2026 16:12 UTCData: JSON · API

Apache Software Foundation Apache Camel

Apache Camel: Camel-Azure-Storage-Blob: the downloadBlobToFile operation built the local download target from the remote blob name without constraining it to the configured fileDir

Relative path traversal vulnerability in Apache Camel Azure Storage Blob 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-blob component can download an Azure Storage blob to the local filesystem through its downloadBlobToFile operation, writing into the directory named by the fileDir endpoint option, which is documented as usable from both the producer and the consumer. BlobOperations.downloadBlobToFile built the local target by joining fileDir with the remote blob name exactly as the Azure SDK reported it (new File(fileDir, client.getBlobName())) 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 blob name is not route-controlled data: the consumer enumerates the container in BlobConsumer.createBatchExchangesFromContainer, which lists blobs and creates one exchange per entry from BlobItem.getName() verbatim, applying no name filtering by default. A blob 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 container 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. Azure Storage blob containers use a flat namespace in which the blob name is an opaque key, so a name carrying such segments is stored and listed as given. 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-blob 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 blob 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; the prefix option can additionally narrow the listing server-side, noting that when both are set regex takes priority and prefix is ignored. Alternatively, avoid the downloadBlobToFile operation on untrusted containers 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 blob names in any externally writable container as untrusted input and do not derive local filesystem paths from them.

First public PoC 1 h beforebefore publication · 24 Aug 2026
Public PoCs11 on GitHub
CVSS9.1critical · scored by CISA ADP · CWE-23
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Apache Software Foundation Apache Camel
  • >= 4.0.0, < 4.14.9
  • >= 4.15.0, < 4.18.4
  • >= 4.19.0, < 4.22.0

Fixed in 4.14.9, 4.18.4, 4.22.0

Mitigation

Upgrade Apache Camel to 4.14.9 or 4.18.4 or 4.22.0 or later.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8First public PoC24 Aug 2026 · t−1hCVE published24 Aug 2026 · t = 0

First public PoC 1 h before publication; not in CISA KEV. First PoC: oscerd/CVE-2026-66906 (created 24 Aug 2026, found by us: backfilled).

PoC repositories

Found on GitHub.

1 PoCs

PoCs 1
RepositoryCreatedStarsAssessment
oscerd/CVE-2026-66906 24 Aug 2026 −1 h 0 PoC

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.

PoC characteristics

What to hunt for in your logs · from 1 PoC repo

Regex

Generated from PoC characteristics; not yet reviewed. Matches the request path and query.

GET /exploit/attack
(?i)^/exploit/attack(?:[?#].*)?$

Suricata

Template generated from PoC characteristics. Review before deploying.

GET /exploit/attack
alert http any any -> $HOME_NET [8080] (msg:"GG PoC-Monitor CVE-2026-66906 Apache Software Foundation Apache Camel exploit attempt"; flow:established,to_server; http.method; content:"GET"; http.uri; content:"/exploit/attack"; reference:url,poc.griffinguard.io/cve/CVE-2026-66906; classtype:web-application-attack; sid:9459461; rev:1;)

Sigma

Template generated from PoC characteristics. Review before deploying.

GET /exploit/attack
title: Apache Software Foundation Apache Camel exploit attempt (CVE-2026-66906)
id: gg-pocmon-cve-2026-66906-9459461
status: experimental
description: Request pattern taken from public PoCs for CVE-2026-66906. Generated, not reviewed.
references:
  - https://poc.griffinguard.io/cve/CVE-2026-66906
logsource:
  category: webserver
detection:
  selection:
    cs-method: GET
    cs-uri-stem|contains|all:
      - '/exploit/attack'
  condition: selection
falsepositives:
  - Authorized vulnerability scanning
level: critical
tags:
  - attack.initial_access
  - attack.t1190
  - cve.2026.66906