Skip to main content
Vulnerability Database/CVE-2026-85315

CVE-2026-85315: Apache Camel gRPC Information Disclosure

CVE-2026-85315 is an information disclosure flaw in Apache Camel gRPC component that exposes sensitive error messages to external clients. This article covers technical details, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-85315 Overview

CVE-2026-85315 is an information disclosure vulnerability in the Apache Camel gRPC component. When a route behind a gRPC consumer fails, the framework copies the exception message into the gRPC status description. The description is transmitted to the calling client, unlike the status cause which remains local to the server. An external caller able to provoke a failure can read internal error messages, which commonly include class and package names, file paths, host names, and connection details. The issue is tracked as CWE-209: Generation of Error Message Containing Sensitive Information and affects Apache Camel versions 4.0.0 through 4.18.4 and 4.19.0 through 4.22.0.

Critical Impact

Remote unauthenticated callers can harvest internal exception messages from gRPC responses, exposing infrastructure details useful for further attacks.

Affected Products

  • Apache Camel gRPC component versions 4.0.0 through 4.18.4
  • Apache Camel gRPC component versions 4.19.0 through 4.22.0
  • Deployments on the 4.18.x and 4.22.x LTS release streams prior to the fix

Discovery Timeline

  • 2026-10-19 - CVE-2026-85315 published to NVD
  • 2026-10-19 - Last updated in NVD database

Technical Details for CVE-2026-85315

Vulnerability Analysis

The Apache Camel gRPC consumer handles route failures by constructing a gRPC Status object. The framework places the raw exception message into the status description field via Status.withDescription(). Because gRPC serializes the description back to the client over the wire, any information embedded in the exception text leaves the server boundary.

Examples of leaked content include fully qualified class names, JAR package paths, backend host names, JDBC connection strings, and file system locations referenced in stack-less exception messages. The disclosed data supports reconnaissance by revealing the internal technology stack, network topology, and service dependencies. This vulnerability belongs to the same unmuted-consumer-exception family as the knative, mina, and CXF Apache Camel advisories released in parallel.

Root Cause

The gRPC consumer did not sanitize or suppress exception messages before serializing them into outbound gRPC status responses. The code path treated the server-side exception text as safe for client consumption, violating the error-handling boundary expected for externally reachable endpoints.

Attack Vector

An unauthenticated remote attacker invokes a gRPC method served by a vulnerable Camel route. The attacker triggers a failure condition such as malformed input, missing resources, or boundary violations. The resulting gRPC response contains the server's exception message in the status description. The attacker parses the response to extract paths, hostnames, and configuration details. See the Apache Camel CVE-2026-85315 Advisory for a full description of the exposure.

No verified exploit code is published. Refer to the vendor advisory and
[Apache JIRA Issue CAMEL-24478](https://issues.apache.org/jira/browse/CAMEL-24478)
for technical details on the error-handling flow.

Detection Methods for CVE-2026-85315

Indicators of Compromise

  • Outbound gRPC responses containing fully qualified Java class names, package prefixes such as org.apache.camel, or stack frame fragments in the status description field.
  • Response descriptions revealing internal hostnames, IP addresses, JDBC URLs, or filesystem paths from backend systems.
  • Repeated client requests designed to trigger error conditions on the same gRPC method, suggesting enumeration behavior.

Detection Strategies

  • Inspect gRPC server logs for exceptions correlated with non-OK status responses that include verbose descriptions returned to clients.
  • Compare the running camel-grpc component version against the fixed releases 4.18.5, 4.22.1, and 4.23.0.
  • Review application code for custom onException handlers that may already overwrite the status description.

Monitoring Recommendations

  • Enable access logging on gRPC endpoints and alert on bursts of failed calls from a single source.
  • Monitor response payload sizes on error paths for anomalous growth that may indicate leaked exception messages.
  • Track dependency inventories for org.apache.camel:camel-grpc to flag outdated versions during CI/CD builds.

How to Mitigate CVE-2026-85315

Immediate Actions Required

  • Upgrade Apache Camel to version 4.23.0 to receive the full fix for the gRPC consumer.
  • Users on the 4.18.x LTS stream should upgrade to 4.18.5; users on the 4.22.x LTS stream should upgrade to 4.22.1.
  • Audit all gRPC-exposed Camel routes and review historical error logs for messages that may have already been disclosed.

Patch Information

The fix introduces a muteException consumer option that defaults to true. When enabled, the framework places a generic description in the gRPC status instead of the route exception's message. Setting muteException=false restores the pre-patch behavior for backward compatibility. Review the referenced GitHub Pull Request #25839, GitHub Pull Request #25934, and GitHub Pull Request #25935 for the implementation details.

Workarounds

  • For deployments that cannot upgrade immediately, add an onException handler to every gRPC-fronted route that maps failures onto an explicit gRPC status, preventing the framework from copying raw exception messages.
  • Place a reverse proxy or API gateway in front of the gRPC endpoint to strip or normalize status description fields on error responses.
  • Review and sanitize custom exception types to ensure their messages do not embed sensitive configuration data.
bash
# Configuration example: enable the mute option after upgrading
# camel-grpc consumer URI
from("grpc://0.0.0.0:50051/org.example.PingService?muteException=true")
    .to("direct:process");

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.