Description
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.
Published: 2026-10-19
Score: 5.3 Medium
EPSS: n/a
KEV: No
Impact: Information Disclosure
Action: Apply Patch
AI Analysis

Impact

A failure in the Apache Camel Knative HTTP consumer results in an unmuted exception being written back to the caller. The exception payload contains the class name, message, stack trace, and potentially configuration details such as file paths or connection strings. This information can be leveraged by attackers to gain insight into the application structure, environment, and underlying services, thereby increasing the effectiveness of subsequent targeted attacks. The weakness is identified as CWE‑209, a failure to restrict log coverage and error information.

Affected Systems

The vulnerability is present in Apache Camel releases 4.0.0 through 4.18.4 and in releases 4.19.0 through 4.22.0. Users on the 4.18.x LTS stream should upgrade to 4.18.5, users on the 4.22.x LTS stream to 4.22.1, and all users can update to the 4.23.0 version where the muteException option defaults to true and the response body is suppressed on failure.

Risk and Exploitability

The CVSS score is 5.3, indicating moderate severity. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog, suggesting no known active exploitation. The attack vector is likely remote through an HTTP endpoint exposed by the Knative consumer; an adversary can trigger failures by sending malformed or otherwise problematic requests and then inspect the detailed error response. Because the failure message is transmitted in cleartext over the network, confidentiality is compromised and the risk circumvents basic authentication or transport encryption if not properly configured.

Generated by OpenCVE AI on October 19, 2026 at 11:38 UTC.

Remediation

Vendor Solution

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.


Vendor Workaround

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.


OpenCVE Recommended Actions

  • Upgrade Apache Camel to version 4.23.0 or upgrade the relevant LTS stream to 4.18.5 or 4.22.1, as the fix restores default muteException behaviour.
  • Configure the consumer to use muteException=true so that failures return an empty body with the error status; the default after the upgrade already provides this protection.
  • If immediate upgrade is not feasible, add an onException handler that sets a custom response body, preventing the framework from writing the exception back to the caller.

Generated by OpenCVE AI on October 19, 2026 at 11:38 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 19 Oct 2026 16:45:00 +0000

Type Values Removed Values Added
First Time appeared Apache
Apache apache Camel
Apache camel
Vendors & Products Apache
Apache apache Camel
Apache camel

Mon, 19 Oct 2026 10:45:00 +0000

Type Values Removed Values Added
Description 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.
Title Apache Camel: Camel-Knative Information Disclosure via Unmuted Consumer Exceptions
Weaknesses CWE-209
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N'}


Subscriptions

Apache Apache Camel Camel
cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-10-19T10:31:08.913Z

Reserved: 2026-09-01T09:26:35.924Z

Link: CVE-2026-84180

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-19T11:17:22.100

Modified: 2026-10-19T11:17:22.100

Link: CVE-2026-84180

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-19T16:30:13Z

Weaknesses
  • CWE-209

    Generation of Error Message Containing Sensitive Information