This is an automated email from the ASF dual-hosted git repository. oscerd pushed a commit to branch new-wave-of-cves in repository https://gitbox.apache.org/repos/asf/camel-website.git
commit 601911549ab9928c4113790dfeecc4de3e19bedd Author: Andrea Cosentino <[email protected]> AuthorDate: Fri Sep 4 09:09:42 2026 +0200 Added CVE-2026-85249 Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_013qz9ir11vuQYfQApzwHAHD Signed-off-by: Andrea Cosentino <[email protected]> --- content/security/CVE-2026-85249.md | 21 ++++++++++++++++++++ content/security/CVE-2026-85249.txt.asc | 35 +++++++++++++++++++++++++++++++++ 2 files changed, 56 insertions(+) diff --git a/content/security/CVE-2026-85249.md b/content/security/CVE-2026-85249.md new file mode 100644 index 00000000..ae834c0d --- /dev/null +++ b/content/security/CVE-2026-85249.md @@ -0,0 +1,21 @@ +--- +title: "Apache Camel Security Advisory - CVE-2026-85249" +date: 2026-08-31T10:00:00+02:00 +url: /security/CVE-2026-85249.html +draft: false +type: security-advisory +cve: CVE-2026-85249 +severity: MEDIUM +summary: "Camel-Tika: header injection - metadata parsed out of the submitted document was mapped onto the Exchange as headers without filtering, so the document could set headers the route relies on, such as CamelFileName" +description: "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 wri [...] +mitigation: "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 Ti [...] +credit: "This issue was discovered by Claude Security Scan Tool" +affected: "From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1." +fixed: 4.18.5, 4.22.1 and 4.23.0 +--- + +The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-24423 refers to the various commits that resolved the issue, and has more details. + +The fix was merged on main in https://github.com/apache/camel/pull/25819 (commit b6f6b4708543677a8b6032304c66cbe7f687a2fb), backported to camel-4.22.x in https://github.com/apache/camel/pull/25940 (commit 260989268cbc6d258b1fcba63770be8ebbec40cb) and to camel-4.18.x in https://github.com/apache/camel/pull/25942 (commit af1efbcccf5882b1ef0094db718972da3190e7e9). + +The issue is classified as CWE-20 Improper Input Validation. The camel-4.14.x line reached end of life before this fix and does not receive it; deployments on 4.14.x should move to 4.18.5 or later. diff --git a/content/security/CVE-2026-85249.txt.asc b/content/security/CVE-2026-85249.txt.asc new file mode 100644 index 00000000..b5d9f60f --- /dev/null +++ b/content/security/CVE-2026-85249.txt.asc @@ -0,0 +1,35 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +- --- +title: "Apache Camel Security Advisory - CVE-2026-85249" +date: 2026-08-31T10:00:00+02:00 +url: /security/CVE-2026-85249.html +draft: false +type: security-advisory +cve: CVE-2026-85249 +severity: MEDIUM +summary: "Camel-Tika: header injection - metadata parsed out of the submitted document was mapped onto the Exchange as headers without filtering, so the document could set headers the route relies on, such as CamelFileName" +description: "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 wri [...] +mitigation: "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 Ti [...] +credit: "This issue was discovered by Claude Security Scan Tool" +affected: "From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1." +fixed: 4.18.5, 4.22.1 and 4.23.0 +- --- + +The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-24423 refers to the various commits that resolved the issue, and has more details. + +The fix was merged on main in https://github.com/apache/camel/pull/25819 (commit b6f6b4708543677a8b6032304c66cbe7f687a2fb), backported to camel-4.22.x in https://github.com/apache/camel/pull/25940 (commit 260989268cbc6d258b1fcba63770be8ebbec40cb) and to camel-4.18.x in https://github.com/apache/camel/pull/25942 (commit af1efbcccf5882b1ef0094db718972da3190e7e9). + +The issue is classified as CWE-20 Improper Input Validation. The camel-4.14.x line reached end of life before this fix and does not receive it; deployments on 4.14.x should move to 4.18.5 or later. +-----BEGIN PGP SIGNATURE----- + +iQEzBAEBCgAdFiEEJ2Y0ButtuvUpHyYV406fOAL/QQAFAmqabrUACgkQ406fOAL/ +QQAnOwf/dEJIoDtgnpkTPyZICqUVOe+M9PbLJuOLeA7izvBK/qIsvW56XfZfgzBY +dzzuZhuMN8FIqY0b1dof/p34WmLLmUxlWc4rtZQQHLjKqGPpTd9gOpgOYHotc5rA +ODcQxYjREMnp25wfybV+hbqRz8+9S0ihq9hNDsLX4BqeWb3GfLWXkzzWlhKlx2zW +YWklygoRijWPNBt9e3sasiv980nwUURd54DfPiBNY36AoFMTWOC06d27KPF56qyi +89cVaWbajSoxS1rn/YhgRcB/Mjj/umIV3FUYuGETLI/mp2HOvWuUe9E1cpoX94qF +T1jLrHQfhx5XwkP/xFALoYD9jPdEvQ== +=3EpW +-----END PGP SIGNATURE-----
