# CVE-2026-85314: Other in Apache Camel

> Attackers can inject mail.smtp headers via MimeMultipart unmarshalling, bypassing filters and influencing downstream mail producers.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-crhc-jwx9-cr8c

## What is CVE-2026-85314?

CVE-2026-85314 is a medium-severity vulnerability in Apache Camel, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-85314?


## How do I fix CVE-2026-85314?

No fix has been published for CVE-2026-85314 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-85314 being exploited?

There is no known exploitation of CVE-2026-85314 in the wild and no public exploit code.

Public exploit code:

- Reproducer for CVE-2026-85314 — Apache Camel camel-mail MimeMultipart mail.smtp header injection (CWE-20). Camel Spring Boot + Camel Quarkus. (github_poc): https://github.com/oscerd/CVE-2026-85314

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85314 and fix it if it is affected.

What it is: CVE-2026-85314 is a medium-severity vulnerability in Apache Camel, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85314 in the wild and no public exploit code.

Affected product: Apache Camel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85314/ (Markdown: https://insights.sbomify.com/CVE-2026-85314/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85314
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85314
- OSV: https://osv.dev/vulnerability/CVE-2026-85314

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85314/
Summaries are generated and may contain mistakes; the official description above is the record.