CVE-2026-85315
Camel-gRPC: information disclosure - the route exception's message was placed into the gRPC status description, which is transmitted to the caller, so an internal error message reached an external client
Description
When a route behind a gRPC consumer failed, the exception's message was placed into the gRPC status description. Unlike the status cause, which stays local to the server, the description is transmitted to the calling client, so an external caller able to provoke a failure could read the internal error message. What that discloses depends on the exception, and in practice includes class and package names, paths, host names and connection detail carried in messages. This is the gRPC member of the same unmuted-consumer-exception family as the knative, mina and CXF advisories published alongside it.
Mitigation
Credit
This issue was discovered by Claude Security Scan Tool
Notes
The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-24478 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/25839 (commit 3c99874122e0c4dbad655a1e32bbcaf48cee1e67), backported to camel-4.22.x in https://github.com/apache/camel/pull/25934 (commit 9a6e8222085ed12f73ce76f826aeb69e9d111ff8) and to camel-4.18.x in https://github.com/apache/camel/pull/25935 (commit e6986906e41b3e537d3a5d278525bc09b78b4127).
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.