Live › vulnerability › CVE-2026-85249
Go to dashboardThe Apache Camel Tika producer copied every metadata key from a submitted document onto the message as a header without filtering. A crafted file can therefore set headers such as CamelFileName, which downstream components use to decide where content is written.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Applications that use the Apache Camel Tika component to parse uploaded or received documents and then route on the resulting headers are exposed. The document supplier controls the metadata keys, so the risk depends on whether downstream components such as file writers rely on Camel-namespace headers. Teams that do not use camel-tika can skip this.
No product ranges from the sources yet.
mvn dependency:tree | grep camel-tika); affected versions are 4.0.0 up to but not including 4.18.5, and 4.19.0 up to but not including 4.22.1.4.23.0, or to 4.18.5 on the 4.18.x LTS stream, or to 4.22.1 on the 4.22.x LTS stream.removeHeaders("Camel*") after the Tika producer and before any component that acts on those headers.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-85249")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.