CVE-2026-85314: Apache Camel: Camel-Mail Header Injection via Unfiltered mail.smtp Headers in the MimeMultipart Data Format (Incomplete Fix of CVE-2026-46584)
Improper Input Validation vulnerability in Apache Camel Mail component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.
CVE-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.
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. 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache Camelto a version that resolves this vulnerability.Fixed in 4.23.0 - Upgrade
Upgrade
Apache Camelto a version that resolves this vulnerability.Fixed in 4.18.5 - Upgrade
Upgrade
Apache Camelto a version that resolves this vulnerability.Fixed in 4.22.1 - Compensating control
For deployments that cannot upgrade immediately, strip the mail.smtp namespace after the MimeMultipart data format by applying removeHeaders("mail.smtp*") before any mail producer.
Event History
Frequently Asked Questions
Which deployments are exposed?
Deployments using Apache Camel 4.0.0 through 4.18.4 or 4.19.0 through 4.22.0 are affected when they unmarshal multipart messages with the MimeMultipart data format and use a downstream mail producer.
What does an attacker need to exploit this issue?
An external sender needs to provide a crafted multipart message. During unmarshalling, the message can set mail.smtp headers on the Camel Exchange, which can influence how a downstream mail producer connects and sends mail.
Does applying the earlier CVE-2026-46584 fix fully address this path?
No. This issue is an incomplete fix of CVE-2026-46584: the MimeMultipart unmarshalling path still mapped mail.smtp headers without applying the header filter.
What versions resolve the issue?
Upgrade to Apache Camel 4.23.0. For the LTS streams, upgrade to 4.18.5 or 4.22.1, which apply header filtering during MimeMultipart unmarshalling.