High [CVE-2026-42527] Apache ActiveMQ: Deserialization of Untrusted Data vulnerability in Apache Camel.
This high-severity Apache Software Foundation advisory covers CVE-2026-42527 affecting Apache Camel, Apache ActiveMQ Artemis, Apache ActiveMQ Classic.
Android app · Google Play
Monitor future Apache Software Foundation CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
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 products named by the advisory: Apache ActiveMQ Artemis; Apache ActiveMQ Classic.
- 4.14.0 through 4.14.8
- 4.15.0 through 4.18.3
- 4.19.0 through 4.21.0.
Official advisory · high-confidence parse· fetched 2 months ago·verify at source
- 4.14.8
- 4.18.3
- 4.21.0
Official advisory · high-confidence parse· fetched 2 months ago·verify at source
Mitigation
Upgrade to a fixed release: 4.14.8, 4.18.3, 4.21.0. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 2 months ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.