Unfiltered Hazelcast deserialization enables remote code execution
Critical (10.0)Published
CVE-2026-78162 allows remote code execution through two Apache Camel Hazelcast configuration paths missing Java deserialization filters.
- Affected
- Apache Camel Hazelcast 4.0.0–4.18.4 and 4.19.0–4.22.0
- Attack requirements
- Ability to publish to a Hazelcast cluster connected to an affected Camel-managed instance
Impact
An attacker can execute code with the Camel process's privileges. Apache's CVE record assigns CVSS 4.0 score 10.0.
Technical detail
- ReplicatedHazelcastAggregationRepository overrides doStart without calling the superclass, bypassing the filter added for CVE-2026-43865.
- HazelcastDefaultComponent also omits the filter when creating a ClientConfig for client mode without an explicit client configuration.
- Both paths deserialize cluster data inside Hazelcast before Camel processes the exchange.
Remediation
- Upgrade to 4.18.5, 4.22.1, or 4.23.0 and later on the corresponding release line; move unsupported releases to a supported line.
- Until upgrading, supply a configuration with JavaSerializationFilterConfig or inject a pre-built HazelcastInstance with filtering enabled.
- Enable Hazelcast authentication and TLS and restrict cluster access.