CVE-2026-84180
Camel-Knative: information disclosure - a route failure was written back to the remote caller as the response body, so the exception class, message and stack trace of an internal error reached an external sender
Description
When processing of an exchange failed on the consumer side, the Knative HTTP consumer wrote the resulting exception back to the remote caller as the response body, including its class name, message and stack trace. An external sender could therefore provoke a failure and read internal detail about the deployment: class and package names, file system or host names carried in exception messages, and the shape of the route. That detail is useful for building a more targeted attack, and where an exception message embeds configuration or connection strings it is disclosure in its own right. camel-knative was the remaining HTTP-family consumer that had not been aligned with the muteException behaviour established for the other HTTP consumers by CAMEL-23651.
Mitigation
Credit
This issue was discovered by Claude Security Scan Tool
Notes
The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-24428 refers to the various commits that resolved the issue, and has more details.
The fix was merged on main in https://github.com/apache/camel/pull/25685 (commit 22cccdecdebd948bea1bcdd6a184345d013a3b1a), backported to camel-4.22.x in https://github.com/apache/camel/pull/25835 (commit ca9f326ada9703d32badabad2f32c66886ffa470) and to camel-4.18.x in https://github.com/apache/camel/pull/25836 (commit 51e3f9047693120b4dd086dcceba16356f92e0aa).
The issue is classified as CWE-209 Generation of Error Message Containing Sensitive Information. The camel-4.14.x line reached end of life before this fix and does not receive it; deployments on 4.14.x should move to 4.18.5 or later.