CVE-2026-85249: Apache Camel: Camel-Tika Header Injection via Unfiltered Document Metadata
Improper Input Validation vulnerability in Apache Camel Tika component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.
The Tika producer mapped every metadata key parsed out of the submitted document onto the Exchange as a header, with no filter applied. Document metadata is attacker-controlled content: the party that supplies the file chooses the metadata keys it carries. A crafted document could therefore set Exchange headers that the rest of the route depends on, including headers in the Camel namespace such as CamelFileName, which downstream components use to decide where content is written. The pattern is the same header-injection class as the consumer advisories published previously, reached here through parsed file content rather than through a protocol header.
Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. Parsed document metadata is now filtered through a HeaderFilterStrategy before it is mapped onto the Exchange. A route that was reading a metadata-derived header the filter now blocks will see it missing. For deployments that cannot upgrade immediately, strip the Camel namespace after the Tika producer with removeHeaders("Camel") before any component that acts on those headers.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache Camelto a version that resolves this vulnerability.Fixed in 4.23.0 - Compensating control
For deployments that cannot upgrade immediately, add removeHeaders("Camel*") after the Tika producer and before any component that acts on Camel headers.
Event History
Frequently Asked Questions
Which deployments are exposed?
Apache Camel routes using the Tika producer are exposed if they run versions from 4.0.0 before 4.18.5, or from 4.19.0 before 4.22.1, and process documents supplied by an attacker or other untrusted party.
What does an attacker need to exploit this issue?
An attacker needs to provide a crafted document to a route using the Tika producer. The attacker controls metadata keys parsed from that document, which were mapped to Exchange headers without filtering.
What could exploitation affect?
Injected metadata can set headers that later route components rely on, including Camel namespace headers such as CamelFileName. This can influence downstream decisions such as where content is written.
What should teams do if they cannot upgrade immediately?
The provided information identifies upgrading as the remediation: upgrade to Apache Camel 4.23.0, or to 4.18.5 for the 4.18.x LTS stream, or 4.22.1 for the 4.22.x LTS stream. No alternative mitigation is specified.
What compatibility impact can the fix have?
The fix filters parsed metadata through a HeaderFilterStrategy before mapping it to the Exchange. Routes that depend on a metadata-derived header that the filter blocks may no longer receive that header.