CVE-2026-85246
Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel Mina…
- 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 Mina component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. When processing of an exchange failed, the Mina consumer wrote exchange.getException() straight back over the socket to the re…
- 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-85246: Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel Mina… (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 Mina component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. When processing of an exchange failed, the Mina consumer wrote exchange.getException() straight back over the socket to the remote peer. Over a textline codec that hands the peer the exception's class name and message; over the object codec it hands over the serialised exception, cause chain included. A remote peer able to provoke a failure could therefore read internal detail about the deployment - class and package names, and whatever a message or nested cause happens to carry, which in practice can include paths, host names and connection detail. The consumer had no option to suppress this, unlike the HTTP-family consumers aligned by CAMEL-23651. 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 the route exception with a generic one carrying no class name, message or stack trace, while still writing a reply so that a synchronous peer is not left to time out. Set muteException=false to restore the previous behaviour. For deployments that cannot upgrade immediately, add an onException handler that sets the reply body explicitly, so the framework never writes the exception back to the peer.
Last activity 19 Oct 2026. Patch Forecast updates every hour.