{"id":"CVE-2026-85314","title":"Apache Camel: Camel-Mail Header Injection via Unfiltered mail.smtp Headers in the MimeMultipart Data Format (Incomplete Fix of CVE-2026-46584)","summary":"Improper Input Validation vulnerability in Apache Camel Mail component.\n\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.\n\nCVE-2026-46584 addressed mail headers reaching the Exchange without passing t…","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-mail","affected":["org.apache.camel:camel-mail >= 4.0.0 < 4.18.5","org.apache.camel:camel-mail >= 4.19.0 < 4.22.1"],"published":"2026-10-19","updated":"2026-10-19","sourceUpdated":"2026-10-19T10:41:45.323Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-85314","references":[{"url":"https://camel.apache.org/security/CVE-2026-85314.html","label":"Apache Camel Security Advisory - CVE-2026-85314"},{"url":"https://issues.apache.org/jira/browse/CAMEL-24419","label":"CAMEL-24419"},{"url":"https://github.com/apache/camel/pull/25568","label":"Fix on main, released in 4.23.0 (commit c2bcb24814a806ced928e612ce5da1a6e3658234)"},{"url":"https://github.com/apache/camel/pull/25765","label":"Backport to camel-4.22.x, released in 4.22.1 (commit 451d3037ee60544cb2158675959416fec5cc5745)"},{"url":"https://github.com/apache/camel/pull/25766","label":"Backport to camel-4.18.x, released in 4.18.5 (commit e25a496381c1330aea16f26136ce02bb818ccccb)"}],"tags":["cve.org"],"ingestedAt":"2026-10-19T12:27:23.810Z","slug":"CVE-2026-85314","body":"## Overview\n\nImproper Input Validation vulnerability in Apache Camel Mail component.\n\nThis issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.\n\nCVE-2026-46584 addressed mail headers reaching the Exchange without passing through a header filter, but the MimeMultipart data format retained an unfiltered path: unmarshalling a multipart message mapped mail.smtp headers onto the Exchange with no filter applied. Those names sit outside the Camel namespace that consumer filters block, so a message crafted by an external sender could still set them, and the mail.smtp namespace influences how a downstream mail producer connects and sends. This is an incomplete fix of CVE-2026-46584 rather than a new class of defect: a deployment that applied that advisory and considered camel-mail settled remained exposed on this path.\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. The MimeMultipart data format now applies the header filter on unmarshal, closing the path CVE-2026-46584 left open. For deployments that cannot upgrade immediately, strip the namespace after the data format with removeHeaders(\"mail.smtp*\") before any mail producer.\n\n## Affected\n\n- `org.apache.camel:camel-mail >= 4.0.0 < 4.18.5`\n- `org.apache.camel:camel-mail >= 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. The MimeMultipart data format now applies the header filter on unmarshal, closing the path CVE-2026-46584 left open.\n\n### Workarounds\n\nFor deployments that cannot upgrade immediately, strip the namespace after the data format with removeHeaders(\"mail.smtp*\") before any mail producer.","depth":"sunlit","depthScore":36,"depthScoreParts":{"impact":35.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}