CVE-2026-42527

CVE-2026-42527 is a high-severity insecure deserialization vulnerability in org.apache.camel:camel-jms (maven), affecting versions >= 4.14.0, < 4.14.8. It is fixed in 4.14.8, 4.18.3, 4.21.0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Apache Camel: Permissive default ObjectInputFilter pattern admits java.net.** and enables DNS-based information disclosure

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.**).

Impact

Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.

CVE-2026-42527 has a CVSS score of 8.1 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.14.8, 4.18.3, 4.21.0); upgrading removes the vulnerable code path.

Affected versions

org.apache.camel:camel-jms (>= 4.14.0, < 4.14.8) org.apache.camel:camel-jms (>= 4.18.0, < 4.18.3) org.apache.camel:camel-jms (>= 4.19.0, < 4.21.0) org.apache.camel:camel-sjms (>= 4.14.0, < 4.14.8) org.apache.camel:camel-sjms (>= 4.18.0, < 4.18.3) org.apache.camel:camel-sjms (>= 4.19.0, < 4.21.0) org.apache.camel:camel-amqp (>= 4.14.0, < 4.14.8) org.apache.camel:camel-amqp (>= 4.18.0, < 4.18.3) org.apache.camel:camel-amqp (>= 4.19.0, < 4.21.0) org.apache.camel:camel-mina (>= 4.14.0, < 4.14.8) org.apache.camel:camel-mina (>= 4.18.0, < 4.18.3) org.apache.camel:camel-mina (>= 4.19.0, < 4.21.0) org.apache.camel:camel-netty (>= 4.14.0, < 4.14.8) org.apache.camel:camel-netty (>= 4.18.0, < 4.18.3) org.apache.camel:camel-netty (>= 4.19.0, < 4.21.0) org.apache.camel:camel-netty-http (>= 4.14.0, < 4.14.8) org.apache.camel:camel-netty-http (>= 4.18.0, < 4.18.3) org.apache.camel:camel-netty-http (>= 4.19.0, < 4.21.0) org.apache.camel:camel-vertx-http (>= 4.14.0, < 4.14.8) org.apache.camel:camel-vertx-http (>= 4.18.0, < 4.18.3) org.apache.camel:camel-vertx-http (>= 4.19.0, < 4.21.0) org.apache.camel:camel-infinispan (>= 4.14.0, < 4.14.8) org.apache.camel:camel-infinispan (>= 4.18.0, < 4.18.3) org.apache.camel:camel-infinispan (>= 4.19.0, < 4.21.0) org.apache.camel:camel-leveldb (>= 4.14.0, < 4.14.8) org.apache.camel:camel-leveldb (>= 4.18.0, < 4.18.3) org.apache.camel:camel-leveldb (>= 4.19.0, < 4.21.0) org.apache.camel:camel-cassandraql (>= 4.14.0, < 4.14.8) org.apache.camel:camel-cassandraql (>= 4.18.0, < 4.18.3) org.apache.camel:camel-cassandraql (>= 4.19.0, < 4.21.0) org.apache.camel:camel-consul (>= 4.14.0, < 4.14.8) org.apache.camel:camel-consul (>= 4.18.0, < 4.18.3) org.apache.camel:camel-consul (>= 4.19.0, < 4.21.0) org.apache.camel:camel-sql (>= 4.14.0, < 4.14.8) org.apache.camel:camel-sql (>= 4.18.0, < 4.18.3) org.apache.camel:camel-sql (>= 4.19.0, < 4.21.0)

Security releases

org.apache.camel:camel-jms → 4.14.8 (maven) org.apache.camel:camel-jms → 4.18.3 (maven) org.apache.camel:camel-jms → 4.21.0 (maven) org.apache.camel:camel-sjms → 4.14.8 (maven) org.apache.camel:camel-sjms → 4.18.3 (maven) org.apache.camel:camel-sjms → 4.21.0 (maven) org.apache.camel:camel-amqp → 4.14.8 (maven) org.apache.camel:camel-amqp → 4.18.3 (maven) org.apache.camel:camel-amqp → 4.21.0 (maven) org.apache.camel:camel-mina → 4.14.8 (maven) org.apache.camel:camel-mina → 4.18.3 (maven) org.apache.camel:camel-mina → 4.21.0 (maven) org.apache.camel:camel-netty → 4.14.8 (maven) org.apache.camel:camel-netty → 4.18.3 (maven) org.apache.camel:camel-netty → 4.21.0 (maven) org.apache.camel:camel-netty-http → 4.14.8 (maven) org.apache.camel:camel-netty-http → 4.18.3 (maven) org.apache.camel:camel-netty-http → 4.21.0 (maven) org.apache.camel:camel-vertx-http → 4.14.8 (maven) org.apache.camel:camel-vertx-http → 4.18.3 (maven) org.apache.camel:camel-vertx-http → 4.21.0 (maven) org.apache.camel:camel-infinispan → 4.14.8 (maven) org.apache.camel:camel-infinispan → 4.18.3 (maven) org.apache.camel:camel-infinispan → 4.21.0 (maven) org.apache.camel:camel-leveldb → 4.14.8 (maven) org.apache.camel:camel-leveldb → 4.18.3 (maven) org.apache.camel:camel-leveldb → 4.21.0 (maven) org.apache.camel:camel-cassandraql → 4.14.8 (maven) org.apache.camel:camel-cassandraql → 4.18.3 (maven) org.apache.camel:camel-cassandraql → 4.21.0 (maven) org.apache.camel:camel-consul → 4.14.8 (maven) org.apache.camel:camel-consul → 4.18.3 (maven) org.apache.camel:camel-consul → 4.21.0 (maven) org.apache.camel:camel-sql → 4.14.8 (maven) org.apache.camel:camel-sql → 4.18.3 (maven) org.apache.camel:camel-sql → 4.21.0 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.apache.camel:camel-jms to 4.14.8 or later; org.apache.camel:camel-jms to 4.18.3 or later; org.apache.camel:camel-jms to 4.21.0 or later; org.apache.camel:camel-sjms to 4.14.8 or later; org.apache.camel:camel-sjms to 4.18.3 or later; org.apache.camel:camel-sjms to 4.21.0 or later; org.apache.camel:camel-amqp to 4.14.8 or later; org.apache.camel:camel-amqp to 4.18.3 or later; org.apache.camel:camel-amqp to 4.21.0 or later; org.apache.camel:camel-mina to 4.14.8 or later; org.apache.camel:camel-mina to 4.18.3 or later; org.apache.camel:camel-mina to 4.21.0 or later; org.apache.camel:camel-netty to 4.14.8 or later; org.apache.camel:camel-netty to 4.18.3 or later; org.apache.camel:camel-netty to 4.21.0 or later; org.apache.camel:camel-netty-http to 4.14.8 or later; org.apache.camel:camel-netty-http to 4.18.3 or later; org.apache.camel:camel-netty-http to 4.21.0 or later; org.apache.camel:camel-vertx-http to 4.14.8 or later; org.apache.camel:camel-vertx-http to 4.18.3 or later; org.apache.camel:camel-vertx-http to 4.21.0 or later; org.apache.camel:camel-infinispan to 4.14.8 or later; org.apache.camel:camel-infinispan to 4.18.3 or later; org.apache.camel:camel-infinispan to 4.21.0 or later; org.apache.camel:camel-leveldb to 4.14.8 or later; org.apache.camel:camel-leveldb to 4.18.3 or later; org.apache.camel:camel-leveldb to 4.21.0 or later; org.apache.camel:camel-cassandraql to 4.14.8 or later; org.apache.camel:camel-cassandraql to 4.18.3 or later; org.apache.camel:camel-cassandraql to 4.21.0 or later; org.apache.camel:camel-consul to 4.14.8 or later; org.apache.camel:camel-consul to 4.18.3 or later; org.apache.camel:camel-consul to 4.21.0 or later; org.apache.camel:camel-sql to 4.14.8 or later; org.apache.camel:camel-sql to 4.18.3 or later; org.apache.camel:camel-sql to 4.21.0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2026-42527? CVE-2026-42527 is a high-severity insecure deserialization vulnerability in org.apache.camel:camel-jms (maven), affecting versions >= 4.14.0, < 4.14.8. It is fixed in 4.14.8, 4.18.3, 4.21.0. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
  2. How severe is CVE-2026-42527? CVE-2026-42527 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which packages are affected by CVE-2026-42527?
    • org.apache.camel:camel-jms (maven) (versions >= 4.14.0, < 4.14.8)
    • org.apache.camel:camel-sjms (maven) (versions >= 4.14.0, < 4.14.8)
    • org.apache.camel:camel-amqp (maven) (versions >= 4.14.0, < 4.14.8)
    • org.apache.camel:camel-mina (maven) (versions >= 4.14.0, < 4.14.8)
    • org.apache.camel:camel-netty (maven) (versions >= 4.14.0, < 4.14.8)
    • org.apache.camel:camel-netty-http (maven) (versions >= 4.14.0, < 4.14.8)
    • org.apache.camel:camel-vertx-http (maven) (versions >= 4.14.0, < 4.14.8)
    • org.apache.camel:camel-infinispan (maven) (versions >= 4.14.0, < 4.14.8)
    • org.apache.camel:camel-leveldb (maven) (versions >= 4.14.0, < 4.14.8)
    • org.apache.camel:camel-cassandraql (maven) (versions >= 4.14.0, < 4.14.8)
    • org.apache.camel:camel-consul (maven) (versions >= 4.14.0, < 4.14.8)
    • org.apache.camel:camel-sql (maven) (versions >= 4.14.0, < 4.14.8)
  4. Is there a fix for CVE-2026-42527? Yes. CVE-2026-42527 is fixed in 4.14.8, 4.18.3, 4.21.0. Upgrade to this version or later.
  5. Is CVE-2026-42527 exploitable, and should I be worried? Whether CVE-2026-42527 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2026-42527 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2026-42527?
    • Upgrade org.apache.camel:camel-jms to 4.14.8 or later
    • Upgrade org.apache.camel:camel-jms to 4.18.3 or later
    • Upgrade org.apache.camel:camel-jms to 4.21.0 or later
    • Upgrade org.apache.camel:camel-sjms to 4.14.8 or later
    • Upgrade org.apache.camel:camel-sjms to 4.18.3 or later
    • Upgrade org.apache.camel:camel-sjms to 4.21.0 or later
    • Upgrade org.apache.camel:camel-amqp to 4.14.8 or later
    • Upgrade org.apache.camel:camel-amqp to 4.18.3 or later
    • Upgrade org.apache.camel:camel-amqp to 4.21.0 or later
    • Upgrade org.apache.camel:camel-mina to 4.14.8 or later
    • Upgrade org.apache.camel:camel-mina to 4.18.3 or later
    • Upgrade org.apache.camel:camel-mina to 4.21.0 or later
    • Upgrade org.apache.camel:camel-netty to 4.14.8 or later
    • Upgrade org.apache.camel:camel-netty to 4.18.3 or later
    • Upgrade org.apache.camel:camel-netty to 4.21.0 or later
    • Upgrade org.apache.camel:camel-netty-http to 4.14.8 or later
    • Upgrade org.apache.camel:camel-netty-http to 4.18.3 or later
    • Upgrade org.apache.camel:camel-netty-http to 4.21.0 or later
    • Upgrade org.apache.camel:camel-vertx-http to 4.14.8 or later
    • Upgrade org.apache.camel:camel-vertx-http to 4.18.3 or later
    • Upgrade org.apache.camel:camel-vertx-http to 4.21.0 or later
    • Upgrade org.apache.camel:camel-infinispan to 4.14.8 or later
    • Upgrade org.apache.camel:camel-infinispan to 4.18.3 or later
    • Upgrade org.apache.camel:camel-infinispan to 4.21.0 or later
    • Upgrade org.apache.camel:camel-leveldb to 4.14.8 or later
    • Upgrade org.apache.camel:camel-leveldb to 4.18.3 or later
    • Upgrade org.apache.camel:camel-leveldb to 4.21.0 or later
    • Upgrade org.apache.camel:camel-cassandraql to 4.14.8 or later
    • Upgrade org.apache.camel:camel-cassandraql to 4.18.3 or later
    • Upgrade org.apache.camel:camel-cassandraql to 4.21.0 or later
    • Upgrade org.apache.camel:camel-consul to 4.14.8 or later
    • Upgrade org.apache.camel:camel-consul to 4.18.3 or later
    • Upgrade org.apache.camel:camel-consul to 4.21.0 or later
    • Upgrade org.apache.camel:camel-sql to 4.14.8 or later
    • Upgrade org.apache.camel:camel-sql to 4.18.3 or later
    • Upgrade org.apache.camel:camel-sql to 4.21.0 or later

Other vulnerabilities in org.apache.camel:camel-jms

CVE-IDSeverityPackage summary
CVE-2026-43866Highorg.apache.camel:camel-jms: Apache Camel JMS deserialization filter bypassCVE-2026-40860Criticalorg.apache.camel:camel-jms: Apache camel-jms, camel-sjms, camel-sjms2 and camel-amqp: Unsafe Deserialization of JMS ObjectMessageCVE-2026-40453Criticalorg.apache.camel:camel-coap: Apache Camel has an incomplete fix for CVE-2025-27636

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo