Live › vulnerability › CVE-2026-85314
Go to dashboardThe MimeMultipart data format in the Apache Camel mail component copies mail.smtp headers from an incoming multipart message onto the Exchange without filtering them. A message from an external sender can therefore influence how a downstream mail producer connects and sends.
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 on Apache Camel 4.0.0 up to 4.18.5 or 4.19.0 up to 4.22.1 that use the camel-mail component and unmarshal multipart messages with MimeMultipart, especially where those messages come from external senders and feed a mail producer. Deployments that already applied the CVE-2026-46584 fix are still exposed on this path. Systems that do not use MimeMultipart on untrusted mail can skip it.
No product ranges from the sources yet.
mvn dependency:tree | grep camel-mail) and see whether it is below 4.18.5 on the 4.18 line or below 4.22.1 on the 4.22 line4.23.04.18.54.22.1Each 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 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.
This page as .md · .json · in your agent: get_signal("CVE-2026-85314")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.