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.
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| 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 |
Referencias
- 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
- Vector CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L- Debilidad (CWE)
CWE-1173, CWE-502- Plataforma
- Java / Kotlin (Maven)
- Paquete
org.apache.camel:camel-mail- Publicada
- 27.04.2026
- Actualizado
- 11.10.2026 13:20
Fuentes y licencias
OSV / GitHub Advisory Database - GHSA-2vqf-x7g4-7c2g - CC BY 4.0
Historial de vulnerabilidades: org.apache.camel:camel-mail
Todas las vulnerabilidades publicadas de este paquete (Java / Kotlin (Maven)), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.
- Entradas en total
- 4
- Primera → última
- 10.2018 08.2026
- Sin corrección
- 0
- Explotada en ataques
- 0
Distribución por gravedad
- Crítica 1
- Media 2
- Baja 1
Divulgaciones por año
- 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 esta entrada
Identifica las vulnerabilidades de tu aplicación
Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.