CVE-2026-49042 Details

A vulnerability allowing improper input validation has been identified in Apache Camel versions 4.8.0 prior to 4.18.3 and 4.19.0 prior to 4.21.0. This issue arises in the 'camel-langchain4j-tools' and 'camel-langchain4j-agent' components, which improperly handle JSON field names returned by large language models (LLMs) in tool-call responses. The vulnerability allows an attacker to inject arbitrary field names into the tool arguments, including internal Camel control headers. These injected headers can then influence the behavior of downstream producers in the route.

Users are advised to upgrade to Apache Camel version 4.21.0 or, if on the 4.18.x release stream, to upgrade to 4.18.3. After upgrading, only tool argument fields that match declared parameters in the tool specification will be set as Exchange headers. For tools defined without parameter declarations, no argument headers will be passed through from LLM tool calls, which is a breaking change for routes that rely on implicit argument passthrough. To restore argument flow, declare the expected parameters explicitly via the parameter.NAME=TYPE endpoint option. For deployments that cannot upgrade immediately, untrusted headers can be stripped after the tool invocation and explicit parameter schemas can be declared for every tool to constrain the LLM-returned arguments.