Information disclosure via undeclared SOAP route exceptions
Published Oct 19, 2026 · Updated Oct 19, 2026
Information disclosure in Apache Camel CXF allows remote attackers to read internal exception details through SOAP faults. CxfConsumer.checkFailure builds a fault from an undeclared route exception, exposing its message or class name; configured fault details also expose stack traces. Exploitation requires access to a SOAP consumer and a triggerable route failure, with disclosure limited to exception content rather than declared service faults.
Summary
What happened
Information disclosure in Apache Camel CXF allows remote attackers to read internal exception details through SOAP faults. CxfConsumer.checkFailure builds a fault from an undeclared route exception, exposing its message or class name; configured fault details also expose stack traces. Exploitation requires access to a SOAP consumer and a triggerable route failure, with disclosure limited to exception content rather than declared service faults.
The record
- CVE
- CVE-2026-85257
- Published
- Oct 19, 2026
- Updated
- Oct 19, 2026
- Vendor
- Apache Software Foundation
- Product
- Apache Camel
- Classifications
- CWE-209
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 19, 2026CVE publishedPublication date reported by the CVE source.
- Oct 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.0.0 <4.18.5
- Affected versionversion=4.19.0 <4.22.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- CxfConsumerMuteExceptionTest upstream regression reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started