CVE-2026-33454
published 2026-04-27CVE-2026-33454: The Camel-Mail component is vulnerable to Camel message header injection. The custom header filter strategy used by the component (MailHeaderFilterStrategy)…
PriorityP357critical9.4CVSS 3.1
AVNACLPRNUINSUCHIHAL
EPSS
0.62%
46.1th percentile
The Camel-Mail component is vulnerable to Camel message header injection. The custom header filter strategy used by the component (MailHeaderFilterStrategy) only filters the 'out' direction via setOutFilterStartsWith, while it does not configure the 'in' direction via setInFilterStartsWith. As a result, when a Camel application consumes mail through camel-mail (for example via from(\"imap://...\") or from(\"pop3://...\")) the inbound filter check is skipped and Camel-prefixed MIME headers are mapped unfiltered into the Exchange. An attacker who can deliver an email to a mailbox monitored by such a consumer can inject Camel-specific headers that, for some Camel components downstream of the mail consumer (such as camel-bean, camel-exec, or camel-sql), can alter the behaviour of the route. This is the same pattern that was previously addressed in camel-undertow (CVE-2025-30177) and the broader incoming-header filter (CVE-2025-27636 and CVE-2025-29891).
This issue affects Apache Camel: from 3.0.0 before 4.14.6, from 4.15.0 before 4.18.1.
Users are recommended to upgrade to version 4.19.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.1. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.6.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| apache | camel | >= 3.0.0 < 4.14.6 | 4.14.6 |
| apache | camel | >= 4.15.0 < 4.18.1 | 4.18.1 |
CVSS provenance
nvdv3.19.4CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
ghsa5.6MEDIUM
vendor_redhat9.4CRITICAL
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
Apache Camel: Camel-Mail: Camel-Mail: Altered application behavior via header injection
vendor_redhat·2026-04-27·CVSS 9.4
CVE-2026-33454 [CRITICAL] CWE-1173 Apache Camel: Camel-Mail: Camel-Mail: Altered application behavior via header injection
Apache Camel: Camel-Mail: Camel-Mail: Altered application behavior via header injection
A flaw was found in the Camel-Mail component. An attacker can exploit this by sending a specially crafted email to a mailbox monitored by a Camel application. Due to a missing inbound filter, malicious headers within the email are not properly filtered, allowing them to alter the behavior of other components within the Camel application. This could lead to unintended actions or data manipulation.
Package: camel-bean (Red Hat build of Apache Camel 4 for Quarkus 3) - Not affected
Package: camel-mail (Red Hat build of Apache Camel 4 for Quarkus 3) - Affected
Package: camel-sql (Red Hat build of Apache Camel 4 for Quarkus 3) - Not affected
Package: camel-bean (Red Hat build of Apache Camel for Spring B
GHSA
Apache Camel's Camel-Mail component is vulnerable to Camel message header injection
ghsa·2026-04-27·CVSS 5.6
CVE-2026-33454 [MEDIUM] CWE-502 Apache Camel's Camel-Mail component is vulnerable to Camel message header injection
Apache Camel's Camel-Mail component is vulnerable to Camel message header injection
The Camel-Mail component is vulnerable to Camel message header injection. The custom header filter strategy used by the component (MailHeaderFilterStrategy) only filters the 'out' direction via setOutFilterStartsWith, while it does not configure the 'in' direction via setInFilterStartsWith. As a result, when a Camel application consumes mail through camel-mail (for example via from(\"imap://...\") or from(\"pop3://...\")) the inbound filter check is skipped and Camel-prefixed MIME headers are mapped unfiltered into the Exchange. An attacker who can deliver an email to a mailbox monitored by such a consumer can inject Camel-specific headers that, for some Camel components downstream of the mail consumer (su
No detection rules found.
No public exploits indexed.
https://camel.apache.org/security/CVE-2026-33454.htmlhttps://access.redhat.com/errata/RHSA-2026:17668https://access.redhat.com/errata/RHSA-2026:19835https://access.redhat.com/security/cve/CVE-2026-33454https://bugzilla.redhat.com/show_bug.cgi?id=2463181https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33454.json
2026-04-27
Published