CVE-2026-85315: Apache Camel: Camel-gRPC Information Disclosure via Unmuted Consumer Exceptions
Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel gRPC component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.
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.
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. A muteException consumer option, defaulting to true, puts a generic description in the status instead of the route exception's message. Set muteException=false to restore the previous output. For deployments that cannot upgrade immediately, map failures onto an explicit status in an onException handler so the framework never copies the exception message into the description.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache Camelto a version that resolves this vulnerability.Fixed in 4.23.0 - Upgrade
Upgrade
Apache Camelto a version that resolves this vulnerability.Fixed in 4.18.5 - Upgrade
Upgrade
Apache Camelto a version that resolves this vulnerability.Fixed in 4.22.1 - Configuration
For deployments that cannot upgrade immediately, map failures onto an explicit status in an onException handler so the framework never copies the exception message into the gRPC status description.
Apache Camel gRPC consumer onException handler status mapping = explicit status
Event History
Frequently Asked Questions
Which deployments are affected?
Affected deployments use the Apache Camel gRPC component in versions from 4.0.0 before 4.18.5, or from 4.19.0 before 4.22.1, with a route behind a gRPC consumer.
What does an attacker need to do to obtain information?
An external gRPC caller must be able to provoke a failure in a route behind the consumer. The resulting exception message can then be returned in the gRPC status description.
What information may be exposed?
The exposed content depends on the route exception message. Reported examples include class and package names, file paths, host names, and connection details carried in exception messages.
Is the safer error behavior enabled by default?
Yes. The muteException consumer option defaults to true and uses a generic gRPC status description rather than the route exception message. Setting muteException=false restores the prior behavior that returns the exception message.
Which updates address the issue?
Upgrade to Apache Camel 4.23.0. For the 4.18.x LTS stream, upgrade to 4.18.5; for the 4.22.x LTS stream, upgrade to 4.22.1.