Loading vulnerability…
CVE-2026-60093 is a relative path traversal vulnerability in Apache Camel's camel-azure-storage-datalake component. The downloadToFile operation constructed a local download target by joining the configured download directory with an Azure Data Lake path name supplied by the remote listing, without lexical normalization or validation that the resolved target remained within the configured directory. The consumer accepted listed path names without filtering by default, enabling parent-directory segments in attacker-influenced remote names to escape the intended local download boundary. Affected versions are Apache Camel 4.0.0 through 4.14.8, 4.15.0 through 4.18.3, and 4.19.0 through 4.21.x.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository contains two runnable Java proof-of-concept reproducers for CVE-2026-60093 in Apache Camel's camel-azure-storage-datalake component: a Spring Boot variant and a Quarkus variant. Both variants are self-contained and expose an HTTP endpoint on port 8080 that triggers the vulnerable DataLakeFileOperations.downloadToFile code path. Rather than interacting with a live Azure Data Lake Gen2 service, each app directly instantiates DataLakeFileOperations with a stub DataLakeFileClientWrapper whose getFileName() returns an attacker-controlled path and whose downloadToFileWithResponse() writes content to the supplied local path. This accurately reproduces the vulnerable behavior where Camel constructs the destination as new File(fileDir, fileName) without normalization or containment checks. The exploit capability is arbitrary file write outside the configured directory /app/downloads by using a malicious remote filename ../../../../../../tmp/pwned-60093.txt, resulting in a write to /tmp/pwned-60093.txt. Repository structure: top-level README explains the CVE, affected/fixed versions, and usage; camel-spring-boot/ contains a standard Spring Boot app with Application.java, DataLakeTraversalDriver.java, ExploitController.java, Dockerfile, docker-compose, and properties; camel-quarkus/ mirrors the same logic with ExploitResource.java and Quarkus packaging. This is a legitimate educational exploit/reproducer, not merely a detector, and its payload is benign marker content proving traversal-based file write.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.