CVE-2026-85257
Camel-CXF: information disclosure - an exception thrown by the route was described back to the SOAP client in the fault, exposing internal exception types and messages that were never part of the service contract
Description
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.
Mitigation
Credit
This issue was discovered by Claude Security Scan Tool
Notes
The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-24477 refers to the various commits that resolved the issue, and has more details.
The fix was merged on main in https://github.com/apache/camel/pull/25742 (commit fd4fd273e4d1d36c1341cc8cf08405decd8c755c), backported to camel-4.22.x in https://github.com/apache/camel/pull/25934 (commit 9a6e8222085ed12f73ce76f826aeb69e9d111ff8) and to camel-4.18.x in https://github.com/apache/camel/pull/25935 (commit e6986906e41b3e537d3a5d278525bc09b78b4127).
The issue is classified as CWE-209 Generation of Error Message Containing Sensitive Information. The camel-4.14.x line reached end of life before this fix and does not receive it; deployments on 4.14.x should move to 4.18.5 or later.