Apache Camel: Camel-Mina Information Disclosure via Unmuted Consumer Exceptions
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Partial Red Hat: 1 without a fix
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and Red Hat. Impact type from CWE-209.
Summary
Apache Camel's Mina component (CWE-209) sends the exchange exception back to the remote peer when processing fails. With a textline codec, the peer receives the exception's class name and message; with the object codec, it receives the serialised exception with its full cause chain, which can expose class and package names, paths, host names and connection details. The Mina consumer had no option to suppress this, and affected versions are 4.0.0 before 4.18.5 and 4.19.0 before 4.22.1. CVSS 3.1 scores it 5.3 (Medium), CISA has not added it to KEV, and no exploit is referenced.
Written with Claude Haiku 5.5 from the sources below · 2026-11-04
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade to Apache Camel 4.23.0; users on the 4.18.x LTS stream should move to 4.18.5, and users on the 4.22.x LTS stream to 4.22.1. The new muteException consumer option defaults to true and replaces the exception with a generic one that has no class name, message or stack trace, while still sending a reply so synchronous peers do not time out; set muteException=false to restore the old behaviour. If an immediate upgrade is not possible, add an onException handler that sets the reply body explicitly so the framework never writes the exception to the peer.
Written with Claude Haiku 5.5 from the sources below · 2026-11-04
- Fix · CNA Apache Camel (Apache Software Foundation) Fixed in 4.18.5, 4.22.1, 4.23.0
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Apache Camel 4.18.5, 4.22.1
39 records Highest priority Priority HIGH 6 HIGH, 9 MEDIUM, 24 LOW
Other records, highest priority first
- TI-2026-76322 Unsafe deserialization in Apache Camel camel-hazelcastPriority HIGH 82
- TI-2026-76339 Path traversal in Apache Camel azure-files componentPriority HIGH 74
- TI-2026-76330 Path traversal in Apache Camel FTP consumer escapes polled directoryPriority HIGH 74
Vendor assessments
Red Hat
Red Hat rating: Moderate. Red Hat's page for this CVE →
| Product | Status | Plan or fix |
|---|---|---|
| Red Hat Fuse 7 | Affected | No fix planned: Out of support scope |
Timeline
- 2026-10-19 Threatist record created from CVE-2026-85246
- 2026-10-19 Alias added: GHSA-83r5-f6fc-33rj
- 2026-10-20 CISA SSVC decision points changed
- 2026-11-04 EPSS moved to the 50th–90th percentile
- 2026-11-04 Affected versions changed · Red Hat
- 2026-11-04 CVSS score added · Red Hat
References
Patch 5
- Apache Camel Security Advisory - CVE-2026-85246
- CAMEL-24476
- Fix on main, released in 4.23.0 (commit 7af3e74d8448b5f1c6620bbae44d766e3f440704)
- Backport to camel-4.22.x, released in 4.22.1 (commit 9a6e8222085ed12f73ce76f826aeb69e9d111ff8)
- Backport to camel-4.18.x, released in 4.18.5 (commit e6986906e41b3e537d3a5d278525bc09b78b4127)
More Apache Camel vulnerabilities
- TI-2026-76322 Unsafe deserialization in Apache Camel camel-hazelcast CVSS 4.0CRITICAL 10.0
- TI-2026-18973 Apache Camel: Camel-Keycloak: Cross-Realm Token Acceptance Bypass in KeycloakSecurityPolicy CVSS 3.1CRITICAL 9.1
- TI-2026-76339 Path traversal in Apache Camel azure-files component CVSS 3.1CRITICAL 9.1
- TI-2026-76330 Path traversal in Apache Camel FTP consumer escapes polled directory CVSS 3.1CRITICAL 9.1
- TI-2025-20435 Apache Camel: Camel Message Header Injection via Improper Filtering CVSS 3.1MEDIUM 5.6
- TI-2026-34899 Apache Camel: Camel-CXF Message Header Injection via Missing Inbound Filtering CVSS 3.1CRITICAL 9.8
Sources
- CVE-2026-85246 · CVE Program
- CVE-2026-85246 · NVD
- FIRST EPSS
- GHSA-83r5-f6fc-33rj · GitHub Advisory Database · CC BY 4.0
- CVE-2026-85246 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences