{"id":"CVE-2026-85249","title":"Apache Camel: Camel-Tika Header Injection via Unfiltered Document Metadata","summary":"Improper Input Validation vulnerability in Apache Camel Tika component.\n\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.\n\nThe Tika producer mapped every metadata key parsed out of the submitted docum…","severity":"medium","cvss":6.5,"cvssVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","cvssSource":"cna","cwe":["CWE-20"],"vendor":"Apache Software Foundation","product":"org.apache.camel:camel-tika","affected":["org.apache.camel:camel-tika >= 4.0.0 < 4.18.5","org.apache.camel:camel-tika >= 4.19.0 < 4.22.1"],"published":"2026-10-19","updated":"2026-10-19","sourceUpdated":"2026-10-19T10:34:39.838Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-85249","references":[{"url":"https://camel.apache.org/security/CVE-2026-85249.html","label":"Apache Camel Security Advisory - CVE-2026-85249"},{"url":"https://issues.apache.org/jira/browse/CAMEL-24423","label":"CAMEL-24423"},{"url":"https://github.com/apache/camel/pull/25819","label":"Fix on main, released in 4.23.0 (commit b6f6b4708543677a8b6032304c66cbe7f687a2fb)"},{"url":"https://github.com/apache/camel/pull/25940","label":"Backport to camel-4.22.x, released in 4.22.1 (commit 260989268cbc6d258b1fcba63770be8ebbec40cb)"},{"url":"https://github.com/apache/camel/pull/25942","label":"Backport to camel-4.18.x, released in 4.18.5 (commit af1efbcccf5882b1ef0094db718972da3190e7e9)"}],"tags":["cve.org"],"ingestedAt":"2026-10-19T12:27:23.814Z","slug":"CVE-2026-85249","body":"## Overview\n\nImproper Input Validation vulnerability in Apache Camel Tika component.\n\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.\n\nThe 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.\n\nUpgrade 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.\n\n## Affected\n\n- `org.apache.camel:camel-tika >= 4.0.0 < 4.18.5`\n- `org.apache.camel:camel-tika >= 4.19.0 < 4.22.1`\n\n## Remediation\n\nUpgrade 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.\n\n### Workarounds\n\nFor deployments that cannot upgrade immediately, strip the Camel namespace after the Tika producer with removeHeaders(\"Camel*\") before any component that acts on those headers.","depth":"sunlit","depthScore":36,"depthScoreParts":{"impact":35.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}