Live › vulnerability › CVE-2026-85246
Go to dashboardWhen an Apache Camel MINA consumer fails to process an exchange, it writes the exception back over the socket to the remote peer. The peer can read the exception class name, message, or serialised exception with its cause chain, which can expose paths, host names and connection details.
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.
Applications running Apache Camel from 4.0.0 before 4.18.5, or from 4.19.0 before 4.22.1, that expose a MINA consumer to peers who can trigger processing failures. The exposure comes from the MINA consumer returning exception output over the socket, so deployments without MINA consumers are not affected. Teams on 4.18.5, 4.22.1, 4.23.0 or later can skip it.
No product ranges from the sources yet.
camel-mina and note the Apache Camel version, e.g. with mvn dependency:tree | grep camel-mina or by checking the camel-mina version in build files.mina:tcp://... or mina2: endpoints) that accept connections from untrusted peers.4.23.0.4.18.5; if on the 4.22.x LTS stream, upgrade to 4.22.1.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 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.
This page as .md · .json · in your agent: get_signal("CVE-2026-85246")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.