Live › vulnerability › CVE-2026-85315
Go to dashboardWhen a route behind a Camel gRPC consumer fails, the exception message is copied into the gRPC status description, which is sent to the calling client. An external caller who can trigger a failure can read internal details such as class names, paths, host names and connection information.
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 running Apache Camel 4.0.0 to before 4.18.5, or 4.19.0 to before 4.22.1, that expose a gRPC consumer to callers who can trigger route failures. The exposure comes from the gRPC consumer returning the route exception message to the client. Teams without a gRPC consumer in Camel routes can skip it.
No product ranges from the sources yet.
mvn dependency:tree | grep camel-grpc or the lockfile, and compare against the fixed ranges below.grpc:// endpoints) and check whether muteException is set to false on them.camel-grpc to 4.23.0, or to 4.18.5 on the 4.18.x LTS line, or to 4.22.1 on the 4.22.x LTS line.muteException at its default of true, or add an onException handler that maps failures to an explicit status so the exception message never reaches the description.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 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.
This page as .md · .json · in your agent: get_signal("CVE-2026-85315")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.