CVE Catalog

CVE-2026-84180

MediumCVSS 5.3
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Elevated risk
0.65%

51th percentile - higher than 51% of all known CVEs

Summary

A vulnerability in the Apache Camel Knative component causes sensitive exception details to be disclosed in the HTTP response returned to the remote caller. When exchange processing failed on the consumer side, the response body included the exception's class name, message, and stack trace. An external sender could provoke a failure and read internal deployment details such as class and package names, file system or host names, and route structure.

Risk Assessment

Disclosure of internal details can help build a more targeted attack, and where an exception message embeds configuration or connection strings, it is a data leak in its own right. The risk affects organizations using Apache Camel Knative versions from 4.0.0 before 4.18.5 and from 4.19.0 before 4.22.1.

Recommendation

Upgrade Apache Camel to 4.23.0, or for LTS streams upgrade 4.18.x to 4.18.5 and 4.22.x to 4.22.1. If an immediate upgrade is not possible, add an onException handler that explicitly sets the response body so the framework never writes the exception back to the caller.

Related vulnerabilities

Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS