CVE Catalog

CVE-2026-85257

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 CXF component causes sensitive information to be exposed in SOAP error messages. When a route behind a CXF SOAP consumer fails with an exception not declared in the service contract, exception details (class and package names, message content, and optionally stack trace) are returned to the SOAP client in the faultstring or fault detail. 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

An external caller able to provoke a failure can read internal deployment details such as class and package names and exception messages, aiding environment reconnaissance and potentially further attacks. The risk applies to SOAP services exposed through Apache Camel CXF.

Recommendation

Upgrade Apache Camel to 4.23.0, or to 4.18.5 or 4.22.1 for the respective LTS streams. If immediate upgrade is not possible, declare the exceptions the service is allowed to report and map every other failure onto one of them in an onException handler so no undeclared exception reaches the fault.

Related vulnerabilities

Original NVD description (English source)

Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel CXF 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 CXF SOAP consumer failed with an exception the service contract does not declare, the exception was described back to the SOAP client in the fault: CXF copies the message into the SOAP faultstring, and can be configured to place the stack trace in the fault detail. An external caller able to provoke a failure could therefore read internal detail about the deployment - class and package names, and whatever the exception message carries. Declared faults, annotated @WebFault, are a different matter: those are part of the published contract that clients are written against, and suppressing them would break the service rather than protect anything. 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 an undeclared route failure with a generic fault carrying no class name, message or stack trace. Faults the contract declares are reported exactly as before. Set muteException=false to restore the previous output. For deployments that cannot upgrade immediately, declare the exceptions the service is allowed to report and map every other failure onto one of them in an onException handler, so no undeclared exception reaches the fault.

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