Deserialization of Untrusted Data Affecting org.apache.camel:camel-consul package, versions [4.14.0,4.14.8)[4.15.0,4.18.3)[4.19.0,4.21.0)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Deserialization of Untrusted Data vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JAVA-ORGAPACHECAMEL-17890719
- published8 Jul 2026
- disclosed6 Jul 2026
- creditYu Bao, Venkatraman Kumar
Introduced: 6 Jul 2026
NewCVE-2026-42527 (opens in a new tab)How to fix?
Upgrade org.apache.camel:camel-consul to version 4.14.8, 4.18.3, 4.21.0 or higher.
Overview
Affected versions of this package are vulnerable to Deserialization of Untrusted Data due to the default ObjectInputFilter. An attacker can trigger DNS-based information disclosure by sending a Java-serialized payload that deserializes into a collection such as HashMap containing java.net.URL or java.net.InetAddress objects. When Camel accepts the object message and applies the permissive default filter, the deserialization side effects issue outbound network lookups to an attacker-controlled host, leaking information through the DNS query and allowing untrusted serialized data to influence the JVM’s network behavior.
Workarounds
- Configure a JMS-provider-side deserialization allow-list before accepting untrusted
ObjectMessagepayloads: use Apache ActiveMQ ArtemisdeserializationAllowList/deserializationDenyList, or Apache ActiveMQ Classicorg.apache.activemq.SERIALIZABLE_PACKAGES, to block malicious Java-serialized objects from reaching Camel and triggering DNS lookup side effects during deserialization. - If you cannot change the broker, override Camel’s default deserialization rules with an endpoint-level
deserializationFilteror the JVM-wide-Djdk.serialFilterproperty, and include an explicit!java.net.**deny rule ahead of the broaderjava.**allow pattern to preventjava.net.URL/java.net.InetAddressfrom being deserialized.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating object from sequence of bytes is called deserialization. Serialization is commonly used for communication (sharing objects between multiple hosts) and persistence (store the object state in a file or a database). It is an integral part of popular protocols like Remote Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System (JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.
Deserialization of untrusted data (CWE-502) is when the application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, thus allowing the attacker to control the state or the flow of the execution.