CVE-2026-42527 is a high-severity (CVSS 8.1) Deserialization of Untrusted Data vulnerability in org.apache.camel:camel-jms. A fix is available for org.apache.camel:camel-jms — see the affected versions and patch details below.
Apache Camel: Permissive default ObjectInputFilter pattern admits java.net.** and enables DNS-based information disclosure
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-42527.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-42527 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.apache.camel:camel-jms☕org.apache.camel:camel-jms☕org.apache.camel:camel-jms☕org.apache.camel:camel-sjms☕org.apache.camel:camel-sjms☕org.apache.camel:camel-sjms☕org.apache.camel:camel-amqp☕org.apache.camel:camel-amqp+28 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.**).
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.camel:camel-jms | ≥ 4.14.0&&< 4.14.8 | 4.14.8org.apache.camel:camel-jms:4.14.8 |
| ☕Maven | org.apache.camel:camel-jms | ≥ 4.18.0&&< 4.18.3 | 4.18.3org.apache.camel:camel-jms:4.18.3 |
| ☕Maven | org.apache.camel:camel-jms | ≥ 4.19.0&&< 4.21.0 | 4.21.0org.apache.camel:camel-jms:4.21.0 |
| ☕Maven | org.apache.camel:camel-sjms | ≥ 4.14.0&&< 4.14.8 | 4.14.8org.apache.camel:camel-sjms:4.14.8 |
| ☕Maven | org.apache.camel:camel-sjms | ≥ 4.18.0&&< 4.18.3 | 4.18.3org.apache.camel:camel-sjms:4.18.3 |
| ☕Maven | org.apache.camel:camel-sjms | ≥ 4.19.0&&< 4.21.0 | 4.21.0org.apache.camel:camel-sjms:4.21.0 |
Affected Products
camelapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.camel:camel-jms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.camel:camel-jms to 4.14.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-42527 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Moderate: Apache Camel components are susceptible to information disclosure through deserialization of untrusted data. When an attacker provides a specially crafted Java-serialized payload to an affected Camel consumer, the default ObjectInputFilter pattern allows DNS queries to an attacker-controlled host. This…
To mitigate this issue, configure a JVM-wide deserialization filter to explicitly deny `java.net` classes. This can be achieved by setting the system property `-Djdk.serialFilter='!java.net.**;java.**;javax.**;org.apache.camel.**;!*'` when starting the Java Virtual Machine. For aggregation-repository components, use `'!java.net.**;java.**;org.apache.camel.**;!*'`. This may impact functionality if legitimate deserialization of `java.net` classes is required. A restart of the affected Apache Camel application is required for the changes to take effect.Source: Red Hat security advisory for CVE-2026-42527 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat build of Apache Camel 4.18.4 for Spring Boot 3.5.16 | camel-amqp | RHSA-2026:71675 |
Frequently Asked Questions
Is CVE-2026-42527 in your dependencies?
Find it across Maven, including transitive dependencies.