CVE-2026-40473
Deserialization RCE in Apache Camel-mina TCP/UDP Consumer
Publication date: 2026-04-27
Last updated on: 2026-04-28
Assigner: Apache Software Foundation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| apache | camel | 4.19.0 |
| apache | camel | From 3.0.0 (inc) to 4.14.6 (exc) |
| apache | camel | From 4.15.0 (inc) to 4.18.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-502 | The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability occurs when the camel-mina component is used as a TCP or UDP consumer that converts incoming data to ObjectInput without applying ObjectInputFilter or class-loading restrictions. Detection involves identifying if your Apache Camel deployment uses vulnerable versions of camel-mina (from 3.0.0 before 4.14.6, from 4.15.0 before 4.18.2, or from 4.19.0 before 4.20.0) and if it listens on network ports for serialized Java objects.
To detect potential exploitation attempts on your network, you can monitor network traffic on the ports where camel-mina TCP or UDP consumers are running for suspicious serialized Java object payloads.
While no specific detection commands are provided in the resources, general approaches include:
- Use network packet capture tools like tcpdump or Wireshark to capture traffic on the relevant ports and analyze for serialized Java objects.
- Example tcpdump command to capture traffic on port mina_port (replace with actual port): tcpdump -i any port mina_port -w capture.pcap
- Inspect application logs for unexpected exceptions or errors related to deserialization or ObjectInputStream usage.
- Check the Apache Camel version in use to confirm if it falls within the vulnerable ranges.
For precise detection and mitigation, upgrading to the fixed versions (4.20.0, 4.14.6, or 4.18.2 depending on your stream) is strongly recommended.
Can you explain this vulnerability to me?
This vulnerability exists in the Apache Camel camel-mina component, specifically in the MinaConverter.toObjectInput(IoBuffer) method. The method converts an IoBuffer into a java.io.ObjectInputStream without applying any ObjectInputFilter or class-loading restrictions.
When a Camel route uses camel-mina as a TCP or UDP consumer and requests conversion to ObjectInput (for example, via getBody(ObjectInput.class) or @Body ObjectInput), an attacker can send a specially crafted serialized Java object over the network to the MINA consumer port.
This crafted input can trigger arbitrary code execution during the readObject() call within the ObjectInputStream, allowing the attacker to execute code in the context of the application.
How can this vulnerability impact me? :
The vulnerability allows an attacker to remotely execute arbitrary code within the context of the affected application. This means that if your application uses the vulnerable versions of Apache Camel camel-mina component as a TCP or UDP consumer with ObjectInput conversion, an attacker can exploit this to run malicious code on your system.
Such remote code execution can lead to unauthorized access, data compromise, service disruption, or further attacks within your environment.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, users are strongly advised to upgrade their Apache Camel installations to a fixed version.
- Upgrade to Apache Camel version 4.20.0, which contains the fix for this issue.
- If you are using the 4.14.x long-term support (LTS) stream, upgrade to version 4.14.6.
- If you are using the 4.18.x stream, upgrade to version 4.18.2.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify how this vulnerability impacts compliance with common standards and regulations such as GDPR or HIPAA.