CVE-2026-42527: Apache Camel: Permissive default ObjectInputFilter pattern admits java.net.** and enables DNS-based information disclosure
(updated )
Deserialization of Untrusted Data vulnerability in Apache Camel.
The default ObjectInputFilter pattern shipped with several Apache Camel components for defense-in-depth deserialization filtering (‘java.;javax.;org.apache.camel.;!*’, or the no-‘javax.’ variant in the aggregation-repository components) uses a recursive ‘java.**’ glob that admits classes whose hashCode/equals/readObject methods perform network I/O, notably java.net.URL and java.net.InetAddress. When an attacker can deliver a Java-serialized payload to an affected Camel consumer, deserialization of a HashMap (or any collection that calls hashCode on its elements) containing java.net.URL keys causes the JVM to issue DNS queries to the attacker-supplied host during the deserialization side-effect. The class-level filter check passes because the resulting object’s class (HashMap) is allow-listed; the DNS query is observable on an attacker-controlled DNS server, providing an out-of-band side channel. The exposure is highest on the camel-jms family because JmsBinding.extractBodyFromJms invokes ObjectMessage.getObject() unconditionally when mapJmsMessage=true (default). Affected components: camel-jms, camel-sjms, camel-amqp, camel-mina, camel-netty, camel-netty-http, camel-vertx-http, camel-infinispan, and the aggregation repository components camel-leveldb, camel-cassandraql, camel-consul, camel-sql (JDBC aggregation repository). This issue affects Apache Camel: from 4.14.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0.
Users are recommended to upgrade to a version that contains the CAMEL-23372 fix once available: 4.21.0 for the 4.21.x line, 4.18.3 for the 4.18.x line, and 4.14.8 for the 4.14.x line. For deployments that cannot upgrade immediately, configure a JMS-provider-side allow-list (Apache ActiveMQ Artemis ‘deserializationAllowList’ / ‘deserializationDenyList’, Apache ActiveMQ Classic ‘org.apache.activemq.SERIALIZABLE_PACKAGES’) as the primary mitigation, and/or override the in-code default via the endpoint-level ‘deserializationFilter’ option or the JVM-wide ‘-Djdk.serialFilter’ system property with an explicit deny: ‘!java.net.;java.;javax.;org.apache.camel.;!’ (or ‘!java.net.;java.;org.apache.camel.**;!’ for the aggregation-repository components, which do not include javax.**).
References
- camel.apache.org/security/CVE-2026-42527.html
- github.com/advisories/GHSA-8h6p-jvhf-9hcr
- github.com/apache/camel/commit/1b60801edf9864465db7abf391539ee425a53e2c
- github.com/apache/camel/commit/1ea8bf4b20898a570f0ac366c9be07ec300cce8d
- github.com/apache/camel/commit/bc7f8cafd1d4752bf6b5a77c19fe9878258faffb
- github.com/apache/camel/pull/22801
- github.com/apache/camel/pull/22813
- github.com/apache/camel/pull/22815
- github.com/apache/camel/releases/tag/camel-4.14.7
- github.com/apache/camel/releases/tag/camel-4.18.2
- github.com/apache/camel/releases/tag/camel-4.21.0
- issues.apache.org/jira/browse/CAMEL-23372
- nvd.nist.gov/vuln/detail/CVE-2026-42527
Code Behaviors & Features
Detect and mitigate CVE-2026-42527 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →