CVE-2026-43865
Received Received - Intake

Remote Code Execution in Apache Camel Hazelcast Component

Publication date: 2026-07-06

Last updated on: 2026-07-06

Assigner: Apache Software Foundation

Description
Deserialization of Untrusted Data vulnerability in Apache Camel Hazelcast component. The camel-hazelcast component creates and manages Hazelcast instances using a default configuration that applies no Java deserialization filter. When Camel builds the Hazelcast Config itself - that is, when no user-supplied HazelcastInstance, hazelcastConfigUri, or referenced Config bean is provided - neither Hazelcast's JavaSerializationFilterConfig nor a Camel-side ObjectInputFilter is configured, so objects received over the Hazelcast cluster protocol are deserialized inside Hazelcast's own serialization layer (ObjectInputStream.readObject) before Camel ever processes them. An attacker who can join or otherwise reach the Hazelcast cluster can publish a crafted serialized Java object that is then deserialized on every Camel node, resulting in remote code execution. The exposure is present by default and requires no opt-in endpoint configuration: any route using a hazelcast consumer (hazelcast-topic, hazelcast-queue, hazelcast-seda, hazelcast-map, hazelcast-multimap, hazelcast-replicatedmap, hazelcast-list, hazelcast-set), as well as the HazelcastAggregationRepository and HazelcastIdempotentRepository, is affected whenever the managed instance is created from Camel's default configuration. This issue affects Apache Camel: from 4.0.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 version 4.21.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. The fix makes Camel apply a default Hazelcast JavaSerializationFilterConfig (whitelisting the java., javax. and org.apache.camel. class-name prefixes and blacklisting java.net.) to instances it creates from its own default configuration, while leaving any user-supplied Config or HazelcastInstance untouched. For deployments that cannot upgrade immediately, configure a deserialization filter on the Hazelcast instance (Hazelcast JavaSerializationFilterConfig, or the JVM-wide system property -Djdk.serialFilter=!java.net.**;java.**;javax.**;org.apache.camel.**;!*) and enable Hazelcast cluster authentication and TLS to restrict who can reach the cluster.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-06
Last Modified
2026-07-06
Generated
2026-07-06
AI Q&A
2026-07-06
EPSS Evaluated
N/A
NVD
CVE-2026-43865
EUVD
EUVD-2026-41826

Affected Vendors & Products

Showing 8 associated CPEs
Vendor Product Version / Range
apache camel 4.0.0
apache camel 4.14.8
apache camel 4.15.0
apache camel 4.18.3
apache camel 4.21.0
apache camel From 4.0.0 (inc) to 4.14.8 (exc)
apache camel From 4.15.0 (inc) to 4.18.3 (exc)
apache camel From 4.19.0 (inc) to 4.21.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-502 The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-43865 is a vulnerability in the Apache Camel camel-hazelcast component involving unsafe Java deserialization. When Camel creates Hazelcast instances using its default configuration, it does not apply any Java deserialization filters. This means that objects received over the Hazelcast cluster protocol are deserialized without restrictions, allowing an attacker who can join or access the Hazelcast cluster to send crafted serialized Java objects. These objects are then deserialized on every Camel node, potentially leading to remote code execution.

The vulnerability affects any route using a hazelcast consumer (such as hazelcast-topic, hazelcast-queue, hazelcast-seda, hazelcast-map, hazelcast-multimap, hazelcast-replicatedmap, hazelcast-list, hazelcast-set) and repositories like HazelcastAggregationRepository and HazelcastIdempotentRepository when the managed Hazelcast instance is created from Camel's default configuration.

Impact Analysis

This vulnerability can lead to remote code execution on systems running affected versions of Apache Camel using the camel-hazelcast component with default Hazelcast configurations. An attacker who gains access to the Hazelcast cluster can publish malicious serialized Java objects that get deserialized by Camel nodes, allowing the attacker to execute arbitrary code remotely.

Such an impact can compromise the confidentiality, integrity, and availability of your systems and data, potentially leading to unauthorized access, data breaches, or disruption of services.

Mitigation Strategies

To mitigate this vulnerability, users should upgrade Apache Camel to versions 4.14.8, 4.18.3, or 4.21.0, which include fixes that apply default deserialization filters to Hazelcast instances created from Camel's default configuration.

If immediate upgrade is not possible, configure a deserialization filter on the Hazelcast instance using Hazelcast JavaSerializationFilterConfig or set the JVM-wide system property -Djdk.serialFilter=!java.net.**;java.**;javax.**;org.apache.camel.**;!*.

Additionally, enable Hazelcast cluster authentication and TLS to restrict access to the cluster and reduce the risk of unauthorized attackers joining the cluster.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-43865. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart