CVE-2025-29891: falha de média gravidade em Apache Camel
Apache Camel: Camel Message Header Injection through request parameters
Publicada em · Atualizada em
77Vexday Risk Score
Priorize a correção. Ela exploração observada pelo VulnCheck e tem prova de conceito pública.
ssvc Actcvss 4.8epss 76%
da publicação à arma225 dias
Publicada no NVD12 de mar.
1ª PoC+225d
VulnCheck+113d
probabilidade de exploração
76%top 1% das CVEs
exploração observada
simVulnCheck
1 exploit(s) público(s)
O que os fabricantes declaram (VEX)
Declarações oficiais dos fabricantes em formato CSAF/VEX: se o produto deles está afetado, já corrigido ou descartado — e por quê. É afirmação do fabricante, não juízo do Vexday.
Red Hatdocumento VEX ↗
Afetado
4 produtos (13 componentes)
Red Hat Fuse 7 · Red Hat Integration Camel K 1 · Red Hat Process Automation 7 · Red Hat Single Sign-On 7
workaround: As a workaround, users could use removeHeaders EIP, to filter out anything like ‘cAmel, cAMEL’ etc, or in general everything not starting with ‘Camel’, ‘camel’ or ‘org.apache.camel.’.
Não afetado
2 produtos (6 componentes) — porque o código vulnerável não está presente no produto
Red Hat build of Apache Camel for Spring Boot 4 · Red Hat build of Apache Camel 4 for Quarkus 3
Bypass/Injection vulnerability in Apache Camel.
This issue affects Apache Camel: from 4.10.0 before 4.10.2, from 4.8.0 before 4.8.5, from 3.10.0 before 3.22.4.
Users are recommended to upgrade to version 4.10.2 for 4.10.x LTS, 4.8.5 for 4.8.x LTS and 3.22.4 for 3.x releases.
This vulnerability is present in Camel's default incoming header filter, that allows an attacker to include Camel specific headers that for some Camel components can alter the behaviours such as the camel-bean component, or the camel-exec component.
If you have Camel applications that are directly connected to the internet via HTTP, then an attacker could include parameters in the HTTP requests that are sent to the Camel application that get translated into headers.
The headers could be both provided as request parameters for an HTTP methods invocation or as part of the payload of the HTTP methods invocation.
All the known Camel HTTP component such as camel-servlet, camel-jetty, camel-undertow, camel-platform-http, and camel-netty-http would be vulnerable out of the box.
This CVE is related to the CVE-2025-27636: while they have the same root cause and are fixed with the same fix, CVE-2025-27636 was assumed to only be exploitable if an attacker could add malicious HTTP headers, while we have now determined that it is also exploitable via HTTP parameters. Like in CVE-2025-27636, exploitation is only possible if the Camel route uses particular vulnerable components.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
Produtos afetados
Apache Software Foundation · Apache CamelPoCs públicas encontradas — 1
vulncheckvulncheck.com/xdb/ddfa073917f9não verificado⚠ Recursos públicos, para você avaliar a exposição de sistemas que controla ou está autorizado a testar. Teste apenas com autorização.
CVEs relacionadas — Apache Camel
No mesmo produto, das mais perigosas para as menos.
CVE-2025-27636MEDIUMApache Camel: Camel Message Header Injection via Improper FilteringEPSS 97.1%CVE-2016-8749—CVE-2016-8749EPSS 10.6%CVE-2018-8041—CVE-2018-8041EPSS 9.6%CVE-2017-12633—CVE-2017-12633EPSS 7.2%CVE-2017-12634—CVE-2017-12634EPSS 7.2%CVE-2026-33453CRITICALApache Camel: CoAP URI Query Parameter to Exchange Header Injection in camel-coap Allows Single-Packet Pre-Auth Remote Code ExecutionEPSS 7.2%