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 (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.
Betroffene Software
Klicken Sie auf eine Technologie, um alle zugehörigen Schwachstellen anzuzeigen.
| Plattform | Paket | Anfällige Versionen | Behoben in |
|---|---|---|---|
| Java / Kotlin (Maven) | org.apache.camel:camel-mail | >= 3.0.0, < 4.14.6, >= 4.15.0, < 4.18.1 | 4.14.6, 4.18.1 |
Verweise
- https://nvd.nist.gov/vuln/detail/CVE-2026-33454
- https://github.com/apache/camel/pull/22152
- https://github.com/apache/camel/pull/22151
- https://github.com/apache/camel/pull/22150
- https://github.com/apache/camel/pull/22149
- https://github.com/apache/camel/pull/22148
- https://github.com/apache/camel/pull/22147
- https://github.com/apache/camel/pull/22146
- https://github.com/apache/camel/commit/e074c01a719cccf3b1c2efbd2ff31e60fd6220ce
- https://github.com/apache/camel/commit/5c20de8f047de725e0b32a874cdb5108c3e46558
- https://github.com/apache/camel/commit/540d48e1cb5e492bd1c74bfc5a6e929fcf24fe3b
- https://github.com/apache/camel/commit/3926ab2b7745e36da2cd8e0dc019018bc415aff9
- https://github.com/apache/camel/commit/05cffa5ec05ff2ec3c50a77825625da6e426e7a8
- https://github.com/apache/camel/commit/0307dd4709a8136eba3206701004bcb528bc47fd
- https://github.com/apache/camel
- https://camel.apache.org/security/CVE-2026-33454.html
- https://bugzilla.redhat.com/show_bug.cgi?id=2463181
- https://access.redhat.com/security/cve/CVE-2026-33454
- https://access.redhat.com/errata/RHSA-2026:19835
- https://issues.apache.org/jira/browse/CAMEL-23222
- https://access.redhat.com/errata/RHSA-2026:17668
- CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L- Schwäche (CWE)
CWE-1173, CWE-502- Plattform
- Java / Kotlin (Maven)
- Paket
org.apache.camel:camel-mail- Veröffentlicht
- 27.04.2026
- Aktualisiert
- 11.10.2026 13:20
Quellen und Lizenzen
OSV / GitHub Advisory Database - GHSA-2vqf-x7g4-7c2g - CC BY 4.0
Schwachstellenhistorie: org.apache.camel:camel-mail
Alle veröffentlichten Schwachstellen dieses Pakets (Java / Kotlin (Maven)), neueste zuerst. Zeigt, ob es ein einmaliger Ausrutscher ist oder ein Paket, das man im Auge behalten muss.
- Einträge insgesamt
- 4
- Erste → letzte
- 10.2018 08.2026
- Ohne Fix
- 0
- In Angriffen ausgenutzt
- 0
Verteilung nach Schweregrad
- Kritisch 1
- Mittel 2
- Niedrig 1
Veröffentlichungen pro Jahr
- 2018: 1
- 2019: 0
- 2020: 0
- 2021: 0
- 2022: 0
- 2023: 0
- 2024: 0
- 2025: 0
- 2026: 3
-
Apache Camel's Camel-Mail component is vulnerable to Camel message header injection dieser Eintrag
Erkennen Sie Schwachstellen in Ihrer Anwendung
Mit der DockRay-Integration und aktivierter Softwareinventarisierung prüft DockRay gemeldete Komponentenversionen auf bekannte Schwachstellen und benachrichtigt Sie über bestätigte Treffer. Die Abdeckung hängt von der unterstützten Technologie und den verfügbaren Meldungen ab.