CVE-2026-85257
Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel CXF…
- Risk score
- 42/100
- CVSS
- 5.3 v3.1
- Exploit chance (30 days)
- 0.6%
- Published
- 19 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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 descr…
- Affected
- Apache Camel before 4.18.5, 4.22.1
- Fix
- Upgrade Apache Camel to 4.18.5 or 4.22.1 (whichever matches your release line), or later.
- Exploitation
- No known exploitation
Story map
At a glance
Apache Camel: Red, act today. Apache Camel has a 'Path Traversal' vulnerability in its Azure Files component, allowing an attacker to access files outside the intended directory. An attacker could read, write, or delete files on the remote server.
The flaws
- CVE-2026-85257: Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel CXF… (CVSS 5.3 · EPSS 1%)
- CVE-2026-79986: Path traversal (CVSS 9.1 · EPSS 1%)
- CVE-2026-78162: Unsafe deserialisation can lead to remote code execution (CVSS 9.8 · EPSS 1%)
- CVE-2026-79983: Path traversal (CVSS 9.1 · EPSS 1%)
The fix
Upgrade Apache Camel: 4.18.5 · 4.22.1 · 4.23.0 or later on your release line
Who is exposed: {'products': ['Apache Camel'], 'packages': [], 'versions': ['4.0.0 before 4.18.5', '4.19.0 before 4.22.1']}
Where it stands
- No known exploitation
Connects to
- Same weakness: CWE-209 (CWE-209). 23 other warnings in 30 days
- Same product: Earlier Apache Camel warnings. 23 in the last 90 days
Why it is Yellow
- CVSS 5.3 medium
References
Original description
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.
Last activity 19 Oct 2026. Patch Forecast updates every hour.