---
id: "CVE-2026-84180"
kind: "vulnerability"
aliases: ["CVE-2026-84180"]
title: "Apache Camel Knative: failed requests return exception stack traces to callers"
severity: "medium"
cvss: 5.3
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["apache-camel", "camel-knative", "java", "knative", "package", "self-hosted"]
not_affected_if: ["camel-knative-not-used", "no-knative-http-consumer", "patched-version"]
published_at: "2026-10-19T11:17:22+00:00"
first_seen_at: "2026-10-23T21:57:18+00:00"
updated_at: "2026-10-25T04:25:18+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-84180", "first_seen_at": "2026-10-23T21:57:18+00:00"}]
---

# Apache Camel Knative: failed requests return exception stack traces to callers

When a Knative HTTP consumer route fails, Apache Camel's camel-knative component writes the exception class, message and stack trace back to the caller as the response body. An external sender can trigger failures to learn internal class names, paths, hostnames and route structure, and may see connection details embedded in exception messages.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the Apache Camel version in the project build file (for example `mvn dependency:tree | grep camel-knative`) and see whether it is below `4.18.5` on the 4.18.x line or below `4.22.1` on the 4.22.x line, or in the 4.0.0 to 4.17.x range.
- Look for camel-knative in the dependency tree; if it is absent, the component is not affected.
- Send a request that makes a route fail and confirm whether the response body contains a Java stack trace.

## Fix

- Apache Camel: upgrade to `4.23.0`, or to `4.18.5` on the 4.18.x LTS stream, or `4.22.1` on the 4.22.x LTS stream.
- Without upgrading, set `muteException=false` only if you need the old output; the new default `muteException=true` returns an empty body with the error status.
- Interim workaround: add an onException handler that sets the response body explicitly so the exception is never written to the caller.

## Timeline

- 2026-10-23T21:57:18+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-84180

## From the sources

Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel Knative component.

This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.

When processing of an exchange failed on the consumer side, the Knative HTTP consumer wrote the resulting exception back to the remote caller as the response body, including its class name, message and stack trace. An external sender could therefore provoke a failure and read internal detail about the deployment: class and package names, file system or host names carried in exception messages, and the shape of the route. That detail is useful for building a more targeted attack, and where an exception message embeds configuration or connection strings it is disclosure in its own right. camel-knative was the remaining HTTP-family consumer that had not been aligned with the muteException behaviour established for the other HTTP consumers by CAMEL-23651.

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. The consumer now honours a muteException option that defaults to true, so a route failure returns an empty body with the error status rather than the exception. Set muteException=false to restore the previous output. For deployments that cannot upgrade immediately, add an onException handler that sets the response body explicitly, so that the framework never writes the exception back to the caller.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_