Description
Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel Mina 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, the Mina consumer wrote exchange.getException() straight back over the socket to the remote peer. Over a textline codec that hands the peer the exception's class name and message; over the object codec it hands over the serialised exception, cause chain included. A remote peer able to provoke a failure could therefore read internal detail about the deployment - class and package names, and whatever a message or nested cause happens to carry, which in practice can include paths, host names and connection detail. The consumer had no option to suppress this, unlike the HTTP-family consumers aligned 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. A muteException consumer option, defaulting to true, replaces the route exception with a generic one carrying no class name, message or stack trace, while still writing a reply so that a synchronous peer is not left to time out. Set muteException=false to restore the previous behaviour. For deployments that cannot upgrade immediately, add an onException handler that sets the reply body explicitly, so the framework never writes the exception back to the peer.
Published: 2026-10-19
Score: 5.3 Medium
EPSS: n/a
KEV: No
Impact: Information Disclosure
Action: Patch
AI Analysis

Impact

The Apache Camel Mina consumer, when an exchange fails, writes the raw exception object back over the TCP socket to the remote peer. This behavior exposes internal exception details—including class names, messages, stack traces, file paths, and host information—especially over textline or object codecs. The result is a detectable leakage of sensitive deployment information that can aid attackers in mapping the system or crafting further exploits. The weakness is an unchecked information disclosure (CWE-209) that compromises confidentiality but does not directly allow code execution or denial of service.

Affected Systems

Apache Camel 4.0.0 through 4.18.4, 4.19.x through 4.22.0, and any earlier 4.x releases are vulnerable. Users on the 4.18.x LTS stream must upgrade to 4.18.5; users on the 4.22.x LTS stream must upgrade to 4.22.1; the general issue is fixed starting with 4.23.0.

Risk and Exploitability

The vulnerability carries a CVSS score of 5.3, indicating moderate severity, and there is no EPSS score available. It is not listed in the CISA KEV catalog. The likely attack vector is a remote peer that can provoke a fault—such as sending malformed data or triggering a processing exception—to capture the exception data over the network. While the exposure is limited to information disclosure, the attacker can gain useful details about the application codebase and environment, potentially facilitating further attacks.

Generated by OpenCVE AI on October 19, 2026 at 11:35 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. A muteException consumer option, defaulting to true, replaces the route exception with a generic one carrying no class name, message or stack trace, while still writing a reply so that a synchronous peer is not left to time out. Set muteException=false to restore the previous behaviour.


Vendor Workaround

For deployments that cannot upgrade immediately, add an onException handler that sets the reply body explicitly, so the framework never writes the exception back to the peer.


OpenCVE Recommended Actions

  • Upgrade to one of the fixed releases: 4.23.0 for newest, 4.18.5 for 4.18.x LTS users, or 4.22.1 for 4.22.x LTS users.
  • If an upgrade is not yet possible, enable the muteException consumer option (default true) to replace the thrown exception with a generic placeholder that contains no class name, message or stack trace.
  • Add an onException route handler that sets a generic reply body so the framework never writes the raw exception back to the peer.
  • Restrict network exposure of the Mina endpoint to trusted networks or implement firewall rules to limit untrusted access.
  • Monitor traffic for unexpected exception content and review logs for signs of error propagation to ensure the mitigation is effective.

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

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

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 Mina 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, the Mina consumer wrote exchange.getException() straight back over the socket to the remote peer. Over a textline codec that hands the peer the exception's class name and message; over the object codec it hands over the serialised exception, cause chain included. A remote peer able to provoke a failure could therefore read internal detail about the deployment - class and package names, and whatever a message or nested cause happens to carry, which in practice can include paths, host names and connection detail. The consumer had no option to suppress this, unlike the HTTP-family consumers aligned 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. A muteException consumer option, defaulting to true, replaces the route exception with a generic one carrying no class name, message or stack trace, while still writing a reply so that a synchronous peer is not left to time out. Set muteException=false to restore the previous behaviour. For deployments that cannot upgrade immediately, add an onException handler that sets the reply body explicitly, so the framework never writes the exception back to the peer.
Title Apache Camel: Camel-Mina 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

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-10-19T10:33:16.880Z

Reserved: 2026-09-03T16:24:12.545Z

Link: CVE-2026-85246

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

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

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

Link: CVE-2026-85246

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-19T11:45:17Z

Weaknesses
  • CWE-209

    Generation of Error Message Containing Sensitive Information