Severity:
CVSS 3.1: 6.5 (medium) CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Affected versions:
- Apache Camel (org.apache.camel:camel-tika) 4.0.0 before 4.18.5
- Apache Camel (org.apache.camel:camel-tika) 4.19.0 before 4.22.1
- Apache Camel (org.apache.camel:camel-tika) 4.18.5 unaffected
- Apache Camel (org.apache.camel:camel-tika) 4.22.1 unaffected
- Apache Camel (org.apache.camel:camel-tika) 4.23.0 unaffected
Description:
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.
Solution:
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.
Work Arounds:
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.
Credit:
Claude Security (finder)
Andrea Cosentino (remediation developer)
References:
https://camel.apache.org/security/CVE-2026-85249.html
https://issues.apache.org/jira/browse/CAMEL-24423
https://github.com/apache/camel/pull/25819
https://github.com/apache/camel/pull/25940
https://github.com/apache/camel/pull/25942
https://camel.apache.org/
https://www.cve.org/CVERecord?id=CVE-2026-85249
