CVE-2026-85315: Apache Camel gRPC information disclosure in error messages

CVE-2026-85315 · Severity: medium · CVSS 5.3 · Published 2026-10-19

Apache Camel is an open-source integration framework that routes messages between applications using various protocols including gRPC. When a message route fails, internal error details including class names, file paths, hostnames, and connection information are sent back to the caller in the gRPC response. An attacker who can trigger route failures could read these sensitive internal details to understand the application's structure and infrastructure.

Technologies: Apache Camel. Vendors: Apache.

Quick answers

Is CVE-2026-85315 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-85315 being exploited in the wild.
How severe is CVE-2026-85315?
Medium severity, with a CVSS score of 5.3, published 19 October 2026.
Which products and versions are affected?
Apache Camel 4.0.0 before 4.18.5, 4.19.0 before 4.22.1.
Is there a fix for CVE-2026-85315?
Yes: fixed in 4.18.5, 4.22.1, 4.23.0. Until then: Set the muteException consumer option to true (the default in patched versions), which puts a generic description in the gRPC status instead of the actual exception message. Alternatively, use an onException handler to map failures onto explicit status codes before the exception message can be copied into the description. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-85315 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-85315?
Check whether you run Apache Camel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 4.18.5, 4.22.1, 4.23.0

Set the muteException consumer option to true (the default in patched versions), which puts a generic description in the gRPC status instead of the actual exception message. Alternatively, use an onException handler to map failures onto explicit status codes before the exception message can be copied into the description.

Technical details

The vulnerability is CWE-209: Generation of Error Message Containing Sensitive Information. When a route behind a gRPC consumer throws an exception, the exception message is placed into the gRPC status description field, which is transmitted to the calling client, unlike the status cause which remains server-local. An unauthenticated remote attacker can exploit this by making gRPC requests that trigger route failures to extract internal error details.

Affected products

  • Apache Camel 4.0.0 before 4.18.5, 4.19.0 before 4.22.1

Timeline

  • 2026-10-15: disclosed
  • 2026-10-15: patched: 4.23.0, 4.22.1, 4.18.5

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.