{"answers":{"affected":"6 open source packages ship an affected version, including org.apache.camel:camel-azure-storage-blob. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-66906 in the wild and no public exploit code.","fix":"Upgrade org.apache.camel:camel-azure-storage-blob to a fixed version for your release line: 4.14.9, 4.18.4 or 4.22.0.","what":"CVE-2026-66906 is a critical path traversal vulnerability in Apache Camel, published on 24 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-66906 and fix it if it is affected.\n\nWhat it is: CVE-2026-66906 is a critical path traversal vulnerability in Apache Camel, published on 24 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-66906 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.camel:camel-azure-storage-blob (Maven): affected from 4.0.0; fixed in 4.14.9\n- org.apache.camel:camel-azure-storage-blob (Maven): affected from 4.0.0; fixed in 4.14.9\n- org.apache.camel:camel-azure-storage-blob (Maven): affected from 4.15.0; fixed in 4.18.4\n- org.apache.camel:camel-azure-storage-blob (Maven): affected from 4.15.0; fixed in 4.18.4\n- org.apache.camel:camel-azure-storage-blob (Maven): affected from 4.19.0; fixed in 4.22.0\n- org.apache.camel:camel-azure-storage-blob (Maven): affected from 4.19.0; fixed in 4.22.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-66906/ (Markdown: https://insights.sbomify.com/CVE-2026-66906/index.md)","id":"CVE-2026-66906","markdown":"https://insights.sbomify.com/CVE-2026-66906/index.md","name":"CVE-2026-66906","record":{"aliases":["GHSA-2x37-89hj-2j95"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Camel library","requires_auth":"none","summary":"Attacker can write files outside the configured directory via malicious blob names, potentially escalating privileges. Users of Apache Camel Azure Storage Blob component should upgrade.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"camel","vendor":"apache"}],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-23","name":"Relative Path Traversal"}],"description":"Relative path traversal vulnerability in Apache Camel Azure Storage Blob 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-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.\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 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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2026-08-24","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-08-24T15:29:24Z","kind":"github_poc","ref":"https://github.com/oscerd/CVE-2026-66906","stars":0,"title":"Reproducer for CVE-2026-66906 (Apache Camel camel-azure-storage-blob downloadBlobToFile path traversal) — Camel Spring Boot + Camel Quarkus"}],"tier":"poc_unverified"},"has_fix":true,"headline":"Apache Camel-Azure-Storage-Blob: the downloadBlobToFile operation built the local download target from the remote blob name without constraining it to the configured fileDir","id":"CVE-2026-66906","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"apache:camel","products":["apache:camel"],"type":"path_traversal","year":"2026"},"n_packages":6,"n_references":1,"next":{"headline":"Apache Camel-Google-Storage: the consumer appended the remote object name to the configured downloadFileName directory without constraining the result","id":"CVE-2026-66907"},"packages":[{"ecosystem":"Maven","fixed":["4.14.9"],"introduced":["4.0.0"],"last_affected":[],"package":"org.apache.camel:camel-azure-storage-blob","purl":null,"source":"GHSA-2x37-89hj-2j95"},{"ecosystem":"Maven","fixed":["4.14.9"],"introduced":["4.0.0"],"last_affected":[],"package":"org.apache.camel:camel-azure-storage-blob","purl":"pkg:maven/org.apache.camel/camel-azure-storage-blob","source":"GHSA-2x37-89hj-2j95"},{"ecosystem":"Maven","fixed":["4.18.4"],"introduced":["4.15.0"],"last_affected":[],"package":"org.apache.camel:camel-azure-storage-blob","purl":null,"source":"GHSA-2x37-89hj-2j95"},{"ecosystem":"Maven","fixed":["4.18.4"],"introduced":["4.15.0"],"last_affected":[],"package":"org.apache.camel:camel-azure-storage-blob","purl":"pkg:maven/org.apache.camel/camel-azure-storage-blob","source":"GHSA-2x37-89hj-2j95"},{"ecosystem":"Maven","fixed":["4.22.0"],"introduced":["4.19.0"],"last_affected":[],"package":"org.apache.camel:camel-azure-storage-blob","purl":null,"source":"GHSA-2x37-89hj-2j95"},{"ecosystem":"Maven","fixed":["4.22.0"],"introduced":["4.19.0"],"last_affected":[],"package":"org.apache.camel:camel-azure-storage-blob","purl":"pkg:maven/org.apache.camel/camel-azure-storage-blob","source":"GHSA-2x37-89hj-2j95"}],"prev":{"headline":"Google::Auth versions before 0.06 for Perl run a command named in an external_account credentials JSON via an ungated system call.","id":"CVE-2026-66902"},"products":["Apache Camel"],"published":"2026-08-24","related":[{"cvss_score":10,"headline":"Apache camel-coap allows header injection that can lead to remote code execution","id":"CVE-2026-33453","kev_date_added":null,"published":"2026-04-27"},{"cvss_score":9.9,"headline":"Apache Camel has an incomplete fix for CVE-2025-27636","id":"CVE-2026-40453","kev_date_added":null,"published":"2026-04-27"},{"cvss_score":9.8,"headline":"Apache Camel K: Camel K Tenant repositories reach Maven execution inside operator pod","id":"CVE-2026-80351","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":9.8,"headline":"Apache Camel K: Camel K Master trait serviceAccountName YAML injection lets CR author apply arbitrary objects","id":"CVE-2026-80352","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":9.8,"headline":"Apache Camel: Camel-Atmosphere-Websocket: WebSocket dispatch header injection","id":"CVE-2026-71300","kev_date_added":null,"published":"2026-08-24"},{"cvss_score":9.8,"headline":"Apache Camel-Undertow: the endpoint discarded the undertow-specific header filter strategy in favour of the base HTTP one, so the undertow filtering never ran on endpoint-configured routes","id":"CVE-2026-78329","kev_date_added":null,"published":"2026-08-24"},{"cvss_score":9.8,"headline":"Apache Camel-PQC: The AWS Secrets Manager key-lifecycle manager deserializes persisted key metadata with java.io.ObjectInputStream and no ObjectInputFilter","id":"CVE-2026-43867","kev_date_added":null,"published":"2026-07-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-25","vendors":["Apache Software Foundation"]},"summary":"Attacker can write files outside the configured directory via malicious blob names, potentially escalating privileges. Users of Apache Camel Azure Storage Blob component should upgrade.","url":"https://insights.sbomify.com/CVE-2026-66906/"}