Live › vulnerability › CVE-2026-84180
Go to dashboardWhen a Knative HTTP consumer route fails, Apache Camel's camel-knative component writes the exception class, message and stack trace back to the caller as the response body. An external sender can trigger failures to learn internal class names, paths, hostnames and route structure, and may see connection details embedded in exception messages.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Applications that use the camel-knative component with a Knative HTTP consumer in Apache Camel 4.0.0 through 4.18.x before 4.18.5, or 4.19.0 through 4.22.x before 4.22.1. Exposure depends on whether an outside sender can reach that consumer endpoint and send a request that makes the route fail. Projects that do not use camel-knative, or that run only on patched releases, can skip it.
No product ranges from the sources yet.
mvn dependency:tree | grep camel-knative) and see whether it is below 4.18.5 on the 4.18.x line or below 4.22.1 on the 4.22.x line, or in the 4.0.0 to 4.17.x range.4.23.0, or to 4.18.5 on the 4.18.x LTS stream, or 4.22.1 on the 4.22.x LTS stream.muteException=false only if you need the old output; the new default muteException=true returns an empty body with the error status.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-84180")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.