Live › vulnerability › CVE-2026-85257
Go to dashboardWhen a route behind an Apache Camel CXF SOAP consumer fails with an exception the service contract does not declare, the error is returned to the SOAP client in the fault, exposing class and package names and exception messages. An external caller who can trigger a failure can read internal details about the deployment.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams running Apache Camel 4.0.0 to before 4.18.5, or 4.19.0 to before 4.22.1, that expose a SOAP service through the CXF component. Exposure depends on routes that can fail with exceptions the WSDL does not declare, and on the consumer's fault settings. Teams without CXF SOAP consumers can skip it.
No product ranges from the sources yet.
camel-cxf or camel-cxf-soap below 4.18.5 or in the range 4.19.0 to 4.22.0.muteException=false or otherwise expose stack traces in fault detail.4.23.0, or to 4.18.5 on the 4.18.x LTS stream, or to 4.22.1 on the 4.22.x LTS stream.muteException=true; set muteException=false only if the previous output is required.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-85257")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.