CVE Catalog

CVE-2026-85246

MediumCVSS 5.3
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Elevated risk
0.63%

50th percentile - higher than 50% of all known CVEs

Summary

A vulnerability in the Apache Camel Mina component causes sensitive exception details to be sent back to the remote peer when exchange processing fails. Depending on the codec (textline or object), the peer may receive class names, messages, or even the serialized exception with its cause chain, potentially exposing paths, host names, and connection details. The issue affects Apache Camel versions from 4.0.0 before 4.18.5 and from 4.19.0 before 4.22.1.

Risk Assessment

A remote attacker able to provoke a failure could read internal deployment details such as class and package names, paths, host names, and connection information, aiding further attacks and reconnaissance. The lack of an option to suppress this behavior in affected versions increases the risk of information leakage.

Recommendation

Upgrade to Apache Camel 4.23.0, or to 4.18.5 for the 4.18.x LTS stream and 4.22.1 for the 4.22.x LTS stream. If an immediate upgrade is not possible, add an onException handler that explicitly sets the reply body so the framework never writes the exception back to the peer.

Related vulnerabilities

Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS