Do Son 
TL;DR
The Apache Camel project disclosed eight Apache Camel vulnerabilities across components such as camel-saxon, camel-aws2-s3 and camel-keycloak. The most severe, CVE-2026-90885, is a high-severity XXE flaw that can expose local files. Fixes ship in Camel 4.23.0, 4.22.2 and 4.18.5.
Why It Matters
Apache Camel moves data between systems, so it often handles untrusted messages, files and cloud objects. A flaw in one component can therefore expose credentials or internal services. In addition, several release lines reached end of life before these fixes, and they “will not receive a fix.”
How the Attacks Work
XXE in camel-saxon (High)
CVE-2026-90885 affects XQuery processing. Camel hardened its own XML converters, but a body that was already a Source object went to Saxon with default settings. As a result, an external entity “declared in that body was resolved.” An outside sender could then “read files readable by the Camel process” and trigger outbound requests.
Expression injection in camel-aws2-s3
CVE-2026-95664 stands out among the medium-severity bugs. The S3 producer evaluated object keys from a message header as Simple expressions. So anyone able to name an object in a consumed bucket could have “Simple expressions of their choosing evaluated in the Camel process.” Those expressions can read environment variables and system properties, which often hold credentials.
Token handling flaws
- CVE-2026-94386 (camel-oauth): a shared token cache ignored scope and client secret, so one profile could receive another profile’s token.
- CVE-2026-95663 (camel-keycloak): cached introspection results let expired access tokens work for up to the cache lifetime, 60 seconds by default.
Other medium flaws
- CVE-2026-71569 (camel-a2a): a blind SSRF through IPv6 unique local addresses reached via a host name.
- CVE-2026-95628 and CVE-2026-95629 (camel-docling): path flaws, including an incomplete fix for CVE-2026-40047.
- CVE-2026-101259 (camel-coap): internal error messages leaked to CoAP clients.
Who found the bugs
Several researchers reported these Apache Camel vulnerabilities. Leon Zlobecki found the XXE flaw. Independent researcher Zhixi “Jace” Sun reported the two Docling bugs and the CoAP leak. Meanwhile, Andrea Cosentino of the Apache Software Foundation found the S3, OAuth and Keycloak issues.
Exploitation status
The Apache Camel advisories do not report exploitation in the wild. No public proof-of-concept has been confirmed, and none of these CVEs appears in CISA’s KEV catalog.
Affected Versions
Ranges differ by component. For example, the XXE and CoAP flaws reach back to Camel 4.0.0, while the S3 bug starts at 4.8.0. The Apache Camel security advisories page lists each range.
Patch and Mitigation Steps
- Upgrade to Camel 4.23.0, or to 4.22.2 or 4.18.5 on those release lines, from the Apache Camel download page.
- Move off end-of-life lines, such as 4.19.x to 4.21.x.
- For S3 routes, remove the CamelAwsS3Key header before the producer if you cannot upgrade.
- Set introspectionCacheEnabled=false in Keycloak policies, or disable OAuth token caching for shared profiles.
- After upgrading, set the new outputBaseDirectory option on Docling endpoints.
Since some fixes change default behavior, review the upgrade guide before you patch these Apache Camel vulnerabilities.
Support Our Threat Intelligence
Find our vulnerability reports and weekly recaps helpful? Support our work today and unlock a 100% ad-free reading experience!
Buy Me a Coffee
