CVE-2026-59230
Description
A flaw was found in Apache Camel's camel-mail component. The MimeMultipart data format copies MIME headers from an incoming message onto the Camel message when unmarshalling with headersInline=true, without applying a HeaderFilterStrategy.
An attacker who can provide a crafted MIME message may inject Camel-internal headers into the Exchange. Downstream Camel components may interpret these headers as control inputs and alter route behavior, potentially causing unintended actions or data processing. The actual impact depends on the downstream route and components that process the message.
The vulnerable behavior affects camel-mail versions from 2.17.0 before 4.14.9, from 4.15.0 before 4.18.4, and from 4.19.0 before 4.22.0. The default headersInline=false configuration is not affected because MIME headers are handled as attachments rather than copied to the Camel message headers.
Mitigation
Users should upgrade to Apache Camel 4.14.9, 4.18.4, or 4.22.0, as applicable to their release stream.
Where an upgrade is not immediately possible, keep headersInline=false unless inline MIME headers are required. If headersInline=true must remain enabled, remove Camel-internal headers immediately after the unmarshalling step, before any processor or producer reads Camel control headers. For example, routes may use removeHeaders("Camel*") as a defense-in-depth measure.
Do not unmarshal MIME content from an untrusted sender into a route that dispatches or performs sensitive operations based on message header values. Treat MIME header names received from outside the trust boundary as untrusted input.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 6.5 | N/A | 6.5 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | Low | N/A | Low |
| Integrity Impact | Low | N/A | Low |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory)
An attacker could provide unexpected values and cause a program crash or arbitrary control of resource allocation, leading to excessive consumption of resources such as memory and CPU.
Confidentiality
Technical Impact: Read Memory; Read Files or Directories
An attacker could read confidential data if they are able to control resource references.
Integrity,Confidentiality,Availability
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
An attacker could use malicious input to modify data or possibly alter control flow in unexpected ways, including arbitrary command execution.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
