Severity:
CVSS 3.1: 5.3 (medium) CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Affected versions:
- Apache Camel (org.apache.camel:camel-knative) 4.0.0 before 4.18.5
- Apache Camel (org.apache.camel:camel-knative) 4.19.0 before 4.22.1
- Apache Camel (org.apache.camel:camel-knative) 4.18.5 unaffected
- Apache Camel (org.apache.camel:camel-knative) 4.22.1 unaffected
- Apache Camel (org.apache.camel:camel-knative) 4.23.0 unaffected
Description:
Generation of Error Message Containing Sensitive Information vulnerability in
Apache Camel Knative component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before
4.22.1.
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.
Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS
releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases
stream should upgrade to 4.22.1. The consumer now honours a muteException
option that defaults to true, so a route failure returns an empty body with the
error status rather than the exception. Set muteException=false to restore the
previous output. For deployments that cannot upgrade immediately, add an
onException handler that sets the response body explicitly, so that the
framework never writes the exception back to the caller.
Solution:
Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS
releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases
stream should upgrade to 4.22.1. The consumer now honours a muteException
option that defaults to true, so a route failure returns an empty body with the
error status rather than the exception. Set muteException=false to restore the
previous output.
Work Arounds:
For deployments that cannot upgrade immediately, add an onException handler
that sets the response body explicitly, so that the framework never writes the
exception back to the caller.
Credit:
Claude Security (finder)
Andrea Cosentino (remediation developer)
References:
https://camel.apache.org/security/CVE-2026-84180.html
https://issues.apache.org/jira/browse/CAMEL-24428
https://github.com/apache/camel/pull/25685
https://github.com/apache/camel/pull/25835
https://github.com/apache/camel/pull/25836
https://camel.apache.org/
https://www.cve.org/CVERecord?id=CVE-2026-84180
