CVE-2026-33453

{"id": "CVE-2026-33453", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-33453", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-04-27T00:00:00+00:00"}}], "cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 10.0, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 6.0, "exploitabilityScore": 3.9}, {"type": "Secondary", "source": "0b0ca135-0b70-47e7-9f44-1890c2a1c46c", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 8.1, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 2.2}]}, "affected": [{"source": "security@apache.org", "affectedData": [{"vendor": "Apache Software Foundation", "product": "Apache Camel", "versions": [{"status": "affected", "version": "4.14.0", "versionType": "semver", "lessThanOrEqual": "4.14.5"}, {"status": "affected", "version": "4.18.0", "lessThan": "4.18.1", "versionType": "semver"}, {"status": "affected", "version": "4.19.0", "versionType": "semver"}], "packageName": "org.apache.camel:camel-coap", "collectionURL": "https://repo.maven.apache.org/maven2", "defaultStatus": "unaffected"}]}, {"source": "0b0ca135-0b70-47e7-9f44-1890c2a1c46c", "affectedData": [{"cpes": ["cpe:/a:redhat:apache_camel_spring_boot:4.18"], "vendor": "Red Hat", "product": "Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14", "packageName": "camel-coap", "collectionURL": "https://access.redhat.com/downloads/content/package-browser/", "defaultStatus": "unaffected"}, {"cpes": ["cpe:/a:redhat:jboss_fuse:7"], "vendor": "Red Hat", "product": "Red Hat Fuse 7", "packageName": "apache-camel", "collectionURL": "https://access.redhat.com/downloads/content/package-browser/", "defaultStatus": "unaffected"}, {"cpes": ["cpe:/a:redhat:jboss_fuse:7"], "vendor": "Red Hat", "product": "Red Hat Fuse 7", "packageName": "apache-camel-k-runtime", "collectionURL": "https://access.redhat.com/downloads/content/package-browser/", "defaultStatus": "unaffected"}, {"cpes": ["cpe:/a:redhat:jboss_fuse:7"], "vendor": "Red Hat", "product": "Red Hat Fuse 7", "packageName": "camel-coap", "collectionURL": "https://access.redhat.com/downloads/content/package-browser/", "defaultStatus": "unaffected"}, {"cpes": ["cpe:/a:redhat:jboss_fuse:7"], "vendor": "Red Hat", "product": "Red Hat Fuse 7", "packageName": "camel-coap-starter", "collectionURL": "https://access.redhat.com/downloads/content/package-browser/", "defaultStatus": "unaffected"}, {"cpes": ["cpe:/a:redhat:jboss_enterprise_application_platform:8"], "vendor": "Red Hat", "product": "Red Hat JBoss Enterprise Application Platform 8", "packageName": "camel-coap", "collectionURL": "https://access.redhat.com/downloads/content/package-browser/", "defaultStatus": "unaffected"}, {"cpes": ["cpe:/a:redhat:jbosseapxp"], "vendor": "Red Hat", "product": "Red Hat JBoss Enterprise Application Platform Expansion Pack", "packageName": "camel-coap", "collectionURL": "https://access.redhat.com/downloads/content/package-browser/", "defaultStatus": "unaffected"}]}], "published": "2026-04-27T11:16:01.873", "references": [{"url": "https://camel.apache.org/security/CVE-2026-33453.html", "tags": ["Broken Link"], "source": "security@apache.org"}, {"url": "http://www.openwall.com/lists/oss-security/2026/04/26/3", "tags": ["Mailing List", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}, {"url": "https://access.redhat.com/errata/RHSA-2026:17668", "source": "0b0ca135-0b70-47e7-9f44-1890c2a1c46c"}, {"url": "https://access.redhat.com/security/cve/CVE-2026-33453", "source": "0b0ca135-0b70-47e7-9f44-1890c2a1c46c"}, {"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2463184", "source": "0b0ca135-0b70-47e7-9f44-1890c2a1c46c"}, {"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33453.json", "source": "0b0ca135-0b70-47e7-9f44-1890c2a1c46c"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Secondary", "source": "security@apache.org", "description": [{"lang": "en", "value": "CWE-915"}]}, {"type": "Secondary", "source": "0b0ca135-0b70-47e7-9f44-1890c2a1c46c", "description": [{"lang": "en", "value": "CWE-915"}]}], "descriptions": [{"lang": "en", "value": "Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerability in Apache Camel Camel-Coap component.\n\nApache Camel's camel-coap component is vulnerable to Camel message header injection, leading to remote code execution when routes forward CoAP requests to header-sensitive producers (e.g. camel-exec)\n\nThe camel-coap component maps incoming CoAP request URI query parameters directly into Camel Exchange In message headers without applying any HeaderFilterStrategy. \u00a0 \nSpecifically, CamelCoapResource.handleRequest() iterates over OptionSet.getUriQuery() and calls camelExchange.getIn().setHeader(...) for every query parameter. CoAPEndpoint extends DefaultEndpoint rather than DefaultHeaderFilterStrategyEndpoint, and CoAPComponent does not implement HeaderFilterStrategyComponent; the component contains no references to HeaderFilterStrategy at all.\n\nAs a result, an unauthenticated attacker who can send a single CoAP UDP packet to a Camel route consuming from coap:// can inject arbitrary Camel internal headers (those prefixed with Camel*) into the Exchange. When the route delivers the message to a header-sensitive producer such as camel-exec, camel-sql, camel-bean, camel-file, or template components (camel-freemarker, camel-velocity), the injected headers can alter the producer's behavior. In the case of camel-exec, the CamelExecCommandExecutable and CamelExecCommandArgs headers override the executable and arguments configured on the endpoint, resulting in arbitrary OS command execution under the privileges of the Camel process.\n\nThe producer's output is written back to the Exchange body and returned in the CoAP response payload by CamelCoapResource, giving the attacker an interactive RCE channel without any need for out-of-band exfiltration.\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \nExploitation prerequisites are minimal: a single unauthenticated UDP datagram to the CoAP port (default 5683). CoAP (RFC 7252) has no built-in authentication, and DTLS is optional and disabled by default. Because the protocol is UDP-based, HTTP-layer WAF/IDS controls do not apply.\nThis issue affects Apache Camel: from 4.14.0 through 4.14.5, from 4.18.0 before 4.18.1, 4.19.0.\n\nUsers are recommended to upgrade to version 4.18.1 or 4.19.0, fixing the issue."}, {"lang": "es", "value": "Vulnerabilidad de Modificaci\u00f3n Incontrolada de Atributos de Objeto Determinados Din\u00e1micamente en el componente Camel-Coap de Apache Camel.\n\nEl componente camel-coap de Apache Camel es vulnerable a la inyecci\u00f3n de encabezados de mensajes de Camel, lo que lleva a la ejecuci\u00f3n remota de c\u00f3digo cuando las rutas reenv\u00edan solicitudes CoAP a productores sensibles a encabezados (p. ej., camel-exec).\n\nEl componente camel-coap mapea los par\u00e1metros de consulta URI de las solicitudes CoAP entrantes directamente en los encabezados de mensajes de entrada de Camel Exchange sin aplicar ninguna HeaderFilterStrategy.\nEspec\u00edficamente, CamelCoapResource.handleRequest() itera sobre OptionSet.getUriQuery() y llama a camelExchange.getIn().setHeader(...) para cada par\u00e1metro de consulta. CoAPEndpoint extiende DefaultEndpoint en lugar de DefaultHeaderFilterStrategyEndpoint, y CoAPComponent no implementa HeaderFilterStrategyComponent; el componente no contiene ninguna referencia a HeaderFilterStrategy en absoluto.\n\nComo resultado, un atacante no autenticado que puede enviar un \u00fanico paquete UDP CoAP a una ruta Camel que consume de coap:// puede inyectar encabezados internos arbitrarios de Camel (aquellos prefijados con Camel) en el Exchange. Cuando la ruta entrega el mensaje a un productor sensible a encabezados como camel-exec, camel-sql, camel-bean, camel-file, o componentes de plantilla (camel-freemarker, camel-velocity), los encabezados inyectados pueden alterar el comportamiento del productor. En el caso de camel-exec, los encabezados CamelExecCommandExecutable y CamelExecCommandArgs anulan el ejecutable y los argumentos configurados en el endpoint, lo que resulta en la ejecuci\u00f3n arbitraria de comandos del sistema operativo bajo los privilegios del proceso Camel.\n\nLa salida del productor se escribe de nuevo en el cuerpo del Exchange y es devuelta en la carga \u00fatil de la respuesta CoAP por CamelCoapResource, dando al atacante un canal RCE interactivo sin necesidad de exfiltraci\u00f3n fuera de banda.\n\nLos requisitos previos para la explotaci\u00f3n son m\u00ednimos: un \u00fanico datagrama UDP no autenticado al puerto CoAP (predeterminado 5683). CoAP (RFC 7252) no tiene autenticaci\u00f3n incorporada, y DTLS es opcional y est\u00e1 deshabilitado por defecto. Debido a que el protocolo es basado en UDP, los controles WAF/IDS de capa HTTP no se aplican.\nEste problema afecta a Apache Camel: desde 4.14.0 hasta 4.14.5, desde 4.18.0 antes de 4.18.1, 4.19.0.\n\nSe recomienda a los usuarios actualizar a la versi\u00f3n 4.18.1 o 4.19.0, solucionando el problema."}], "lastModified": "2026-10-26T22:10:00.163", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "A21A0C99-583A-4186-9A63-1A056CE0FE6C", "versionEndIncluding": "4.14.5", "versionStartIncluding": "4.14.0"}, {"criteria": "cpe:2.3:a:apache:camel:4.18.0:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "5AD9BD3F-C8B5-47C7-AA9D-0AF5292076FF"}, {"criteria": "cpe:2.3:a:apache:camel:4.19.0:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "EDA4D206-8808-4D2A-873E-8488DD7E3E16"}], "operator": "OR"}]}], "sourceIdentifier": "security@apache.org"}