# CVE-2026-42527: Apache Camel: Permissive default ObjectInputFilter pattern admits java.net.** and enables DNS-based information disclosure > Attackers can trigger DNS queries via deserialized Java objects in Apache Camel, enabling out-of-band information disclosure. - **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 6 Jul 2026 - **Updated:** 6 Jul 2026 - **Also known as:** GHSA-8h6p-jvhf-9hcr, MINI-cgfr-mrgw-5c69, MINI-hcc3-6rqw-rcfv ## What is CVE-2026-42527? CVE-2026-42527 is a high-severity unsafe deserialization vulnerability in Apache Camel, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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.**). Weakness: CWE-502 (Deserialization of Untrusted Data) ## Which versions are affected by CVE-2026-42527? 40 open source packages ship an affected version, including org.apache.camel:camel-amqp, org.apache.camel:camel-cassandraql and org.apache.camel:camel-consul. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.camel:camel-amqp` | Maven | From 4.14.0 | 4.14.8 | | `org.apache.camel:camel-amqp` | Maven | From 4.14.0 | 4.14.8 | | `org.apache.camel:camel-amqp` | Maven | From 4.18.0 | 4.18.3 | | `org.apache.camel:camel-amqp` | Maven | From 4.18.0 | 4.18.3 | | `org.apache.camel:camel-amqp` | Maven | From 4.19.0 | 4.21.0 | | `org.apache.camel:camel-amqp` | Maven | From 4.19.0 | 4.21.0 | | `org.apache.camel:camel-cassandraql` | Maven | From 4.14.0 | 4.14.8 | | `org.apache.camel:camel-cassandraql` | Maven | From 4.14.0 | 4.14.8 | | `org.apache.camel:camel-cassandraql` | Maven | From 4.18.0 | 4.18.3 | | `org.apache.camel:camel-cassandraql` | Maven | From 4.18.0 | 4.18.3 | | `org.apache.camel:camel-cassandraql` | Maven | From 4.19.0 | 4.21.0 | | `org.apache.camel:camel-cassandraql` | Maven | From 4.19.0 | 4.21.0 | | `org.apache.camel:camel-consul` | Maven | From 4.14.0 | 4.14.8 | | `org.apache.camel:camel-consul` | Maven | From 4.14.0 | 4.14.8 | | `org.apache.camel:camel-consul` | Maven | From 4.18.0 | 4.18.3 | | `org.apache.camel:camel-consul` | Maven | From 4.18.0 | 4.18.3 | | `org.apache.camel:camel-consul` | Maven | From 4.19.0 | 4.21.0 | | `org.apache.camel:camel-consul` | Maven | From 4.19.0 | 4.21.0 | | `org.apache.camel:camel-infinispan` | Maven | From 4.14.0 | 4.14.8 | | `org.apache.camel:camel-infinispan` | Maven | From 4.14.0 | 4.14.8 | | `org.apache.camel:camel-infinispan` | Maven | From 4.18.0 | 4.18.3 | | `org.apache.camel:camel-infinispan` | Maven | From 4.18.0 | 4.18.3 | | `org.apache.camel:camel-infinispan` | Maven | From 4.19.0 | 4.21.0 | | `org.apache.camel:camel-infinispan` | Maven | From 4.19.0 | 4.21.0 | | `org.apache.camel:camel-jms` | Maven | From 4.14.0 | 4.14.8 | | `org.apache.camel:camel-jms` | Maven | From 4.14.0 | 4.14.8 | | `org.apache.camel:camel-jms` | Maven | From 4.18.0 | 4.18.3 | | `org.apache.camel:camel-jms` | Maven | From 4.18.0 | 4.18.3 | | `org.apache.camel:camel-jms` | Maven | From 4.19.0 | 4.21.0 | | `org.apache.camel:camel-jms` | Maven | From 4.19.0 | 4.21.0 | | `org.apache.camel:camel-leveldb` | Maven | From 4.14.0 | 4.14.8 | | `org.apache.camel:camel-leveldb` | Maven | From 4.14.0 | 4.14.8 | | `org.apache.camel:camel-leveldb` | Maven | From 4.18.0 | 4.18.3 | | `org.apache.camel:camel-leveldb` | Maven | From 4.18.0 | 4.18.3 | | `org.apache.camel:camel-leveldb` | Maven | From 4.19.0 | 4.21.0 | | `org.apache.camel:camel-leveldb` | Maven | From 4.19.0 | 4.21.0 | | `org.apache.camel:camel-mina` | Maven | From 4.14.0 | 4.14.8 | | `org.apache.camel:camel-mina` | Maven | From 4.14.0 | 4.14.8 | | `org.apache.camel:camel-mina` | Maven | From 4.18.0 | 4.18.3 | | `org.apache.camel:camel-mina` | Maven | From 4.18.0 | 4.18.3 | Products: Apache Camel. ## How do I fix CVE-2026-42527? Upgrade org.apache.camel:camel-amqp to a fixed version for your release line: 4.14.8, 4.18.3 or 4.21.0. ## Is CVE-2026-42527 being exploited? There is no known exploitation of CVE-2026-42527 in the wild and no public exploit code. Public exploit code: - Reproducer for CVE-2026-42527 — Apache Camel permissive default ObjectInputFilter admits java.net.URL, enabling a DNS-based out-of-band side channel (github_poc): https://github.com/oscerd/CVE-2026-42527 ## Other vulnerabilities in Apache Camel - [CVE-2026-33453](https://insights.sbomify.com/CVE-2026-33453/): Apache camel-coap allows header injection that can lead to remote code execution (critical 10.0) - [CVE-2026-40453](https://insights.sbomify.com/CVE-2026-40453/): Apache Camel has an incomplete fix for CVE-2025-27636 (critical 9.9) - [CVE-2026-80351](https://insights.sbomify.com/CVE-2026-80351/): Apache Camel K: Camel K Tenant repositories reach Maven execution inside operator pod (critical 9.8) - [CVE-2026-80352](https://insights.sbomify.com/CVE-2026-80352/): Apache Camel K: Camel K Master trait serviceAccountName YAML injection lets CR author apply arbitrary objects (critical 9.8) - [CVE-2026-71300](https://insights.sbomify.com/CVE-2026-71300/): Apache Camel: Camel-Atmosphere-Websocket: WebSocket dispatch header injection (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-42527 and fix it if it is affected. What it is: CVE-2026-42527 is a high-severity unsafe deserialization vulnerability in Apache Camel, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-42527 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.camel:camel-amqp (Maven): affected from 4.14.0; fixed in 4.14.8 - org.apache.camel:camel-amqp (Maven): affected from 4.14.0; fixed in 4.14.8 - org.apache.camel:camel-amqp (Maven): affected from 4.18.0; fixed in 4.18.3 - org.apache.camel:camel-amqp (Maven): affected from 4.18.0; fixed in 4.18.3 - org.apache.camel:camel-amqp (Maven): affected from 4.19.0; fixed in 4.21.0 - org.apache.camel:camel-amqp (Maven): affected from 4.19.0; fixed in 4.21.0 - org.apache.camel:camel-cassandraql (Maven): affected from 4.14.0; fixed in 4.14.8 - org.apache.camel:camel-cassandraql (Maven): affected from 4.14.0; fixed in 4.14.8 - org.apache.camel:camel-cassandraql (Maven): affected from 4.18.0; fixed in 4.18.3 - org.apache.camel:camel-cassandraql (Maven): affected from 4.18.0; fixed in 4.18.3 - org.apache.camel:camel-cassandraql (Maven): affected from 4.19.0; fixed in 4.21.0 - org.apache.camel:camel-cassandraql (Maven): affected from 4.19.0; fixed in 4.21.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-42527/ (Markdown: https://insights.sbomify.com/CVE-2026-42527/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-42527 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-42527 - OSV: https://osv.dev/vulnerability/CVE-2026-42527 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-42527/ Summaries are generated and may contain mistakes; the official description above is the record.