CVE-2026-66906
Path traversal in Apache Camel Azure Blob download allows writing files outside configured dir.
Is CVE-2026-66906 being exploited?
Not confirmed. CVE-2026-66906 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.53% probability of exploitation in the next 30 days.
How severe is CVE-2026-66906?
CVE-2026-66906 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-66906?
Yes. A fix has been recorded for CVE-2026-66906. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-66906 affect?
CVE-2026-66906 affects Apache Camel camel-azure-storage-blob versions 4.0.0 to <4.14.9, Apache Camel camel-azure-storage-blob versions 4.15.0 to <4.18.4, Apache Camel camel-azure-storage-blob versions 4.19.0 to <4.22.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-66906?
Upgrade to 4.22.0 (or 4.14.9/4.18.4), or filter blob names (regex) / avoid downloadBlobToFile.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker-controlled blob names can cause Camel to create/overwrite files outside fileDir as the Camel process, enabling file overwrite and potential privilege escalation.
Immediate action required
- affected>= 4.0.0 and < 4.14.9
- affected>= 4.15.0 and < 4.18.4
- affected>= 4.19.0 and < 4.22.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.