{"resultsPerPage":1,"startIndex":0,"totalResults":1,"format":"NVD_CVE","version":"2.0","timestamp":"2026-05-05T08:26:56.488","vulnerabilities":[{"cve":{"id":"CVE-2025-29891","sourceIdentifier":"security@apache.org","published":"2025-03-12T15:15:40.997","lastModified":"2025-04-02T20:37:07.073","vulnStatus":"Analyzed","cveTags":[],"descriptions":[{"lang":"en","value":"Bypass/Injection vulnerability in Apache Camel.\n\nThis 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.\n\nUsers 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.\n\nThis 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.\n\nIf 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. \n\nThe headers could be both provided as request parameters for an HTTP methods invocation or as part of the payload of the HTTP methods invocation.\n\nAll 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.\n\nThis 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."},{"lang":"es","value":"Vulnerabilidad de omisión/inyección en Apache Camel. Este problema afecta a Apache Camel: desde la versión 4.10.0 hasta la 4.10.2, desde la 4.8.0 hasta la 4.8.5, y desde la 3.10.0 hasta la 3.22.4. Se recomienda actualizar a la versión 4.10.2 para la versión 4.10.x LTS, a la 4.8.5 para la versión 4.8.x LTS y a la 3.22.4 para la versión 3.x. Esta vulnerabilidad se presenta en el filtro de encabezados entrantes predeterminado de Camel, que permite a un atacante incluir encabezados específicos de Camel que, en algunos componentes de Camel, pueden alterar el comportamiento, como los componentes camel-bean o camel-exec. Si tiene aplicaciones Camel conectadas directamente a internet mediante HTTP, un atacante podría incluir parámetros en las solicitudes HTTP enviadas a la aplicación Camel que se traducen en encabezados. Los encabezados podrían proporcionarse como parámetros de solicitud para la invocación de métodos HTTP o como parte de la carga útil de dicha invocación. Todos los componentes HTTP conocidos de Camel, como camel-servlet, camel-jetty, camel-undertow, camel-platform-http y camel-netty-http, serían vulnerables de fábrica. Esta CVE está relacionada con la CVE-2025-27636: si bien comparten la misma causa raíz y se corrigen con la misma solución, se asumió que la CVE-2025-27636 solo era explotable si un atacante podía agregar encabezados HTTP maliciosos, mientras que ahora hemos determinado que también es explotable mediante parámetros HTTP. Al igual que en la CVE-2025-27636, la explotación solo es posible si la ruta Camel utiliza componentes vulnerables específicos."}],"metrics":{"cvssMetricV31":[{"source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L","baseScore":4.8,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"HIGH","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"LOW","availabilityImpact":"LOW"},"exploitabilityScore":2.2,"impactScore":2.5}]},"weaknesses":[{"source":"security@apache.org","type":"Secondary","description":[{"lang":"en","value":"CWE-164"}]}],"configurations":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*","versionStartIncluding":"3.10.0","versionEndExcluding":"3.22.4","matchCriteriaId":"F955C7FA-20EE-44FC-BB7F-2734A731A9DC"},{"vulnerable":true,"criteria":"cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.8.0","versionEndExcluding":"4.8.5","matchCriteriaId":"15914F75-761B-40AD-8489-EA92699F3741"},{"vulnerable":true,"criteria":"cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.10.0","versionEndExcluding":"4.10.2","matchCriteriaId":"DB496A7D-7E5D-48DA-B49F-4494B7369026"}]}]}],"references":[{"url":"https://camel.apache.org/security/CVE-2025-27636.html","source":"security@apache.org","tags":["Not Applicable"]},{"url":"https://camel.apache.org/security/CVE-2025-29891.html","source":"security@apache.org","tags":["Vendor Advisory"]},{"url":"https://github.com/akamai/CVE-2025-27636-Apache-Camel-PoC","source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","tags":["Exploit"]}]}}]}