# CVE-2026-85315: Apache Camel: Camel-gRPC Information Disclosure via Unmuted Consumer Exceptions

> An attacker can read internal error details like paths and hostnames from gRPC responses when a route fails, exposing sensitive information.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-xj93-qh7c-f9w3

## What is CVE-2026-85315?

CVE-2026-85315 is a medium-severity vulnerability in Apache Camel, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

## Which versions are affected by CVE-2026-85315?


## How do I fix CVE-2026-85315?

No fix has been published for CVE-2026-85315 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-85315 being exploited?

There is no known exploitation of CVE-2026-85315 in the wild and no public exploit code.

Public exploit code:

- Reproducer for CVE-2026-85315 — Apache Camel camel-grpc consumer exception disclosure (CWE-209). Camel Spring Boot + Camel Quarkus. (github_poc): https://github.com/oscerd/CVE-2026-85315

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85315 and fix it if it is affected.

What it is: CVE-2026-85315 is a medium-severity vulnerability in Apache Camel, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85315 in the wild and no public exploit code.

Affected product: Apache Camel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85315/ (Markdown: https://insights.sbomify.com/CVE-2026-85315/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85315
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85315
- OSV: https://osv.dev/vulnerability/CVE-2026-85315

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85315/
Summaries are generated and may contain mistakes; the official description above is the record.