CVE-2026-78162
Last modified
CVE-2026-78162 is a critical-severity vulnerability rated 10/10 on the CVSS scale. Deserialization of Untrusted Data vulnerability in Apache Camel. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. The camel-hazelcast component applies a default Hazelcast JavaSerializationFilterConfig to the instances it creates from its own configuration, a protection introduced by CVE-2026-43865. That change did not reach two of the configuration paths Camel builds itself, so those paths continued to create Hazelcast instances whose Java deserialization is unrestricted.
Description
Deserialization of Untrusted Data vulnerability in Apache Camel. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. The camel-hazelcast component applies a default Hazelcast JavaSerializationFilterConfig to the instances it creates from its own configuration, a protection introduced by CVE-2026-43865. That change did not reach two of the configuration paths Camel builds itself, so those paths continued to create Hazelcast instances whose Java deserialization is unrestricted. ReplicatedHazelcastAggregationRepository extends HazelcastAggregationRepository but overrides doStart() without calling super.doStart(), keeping its own copy of the bootstrap block, and therefore never received the filter: a route using it without supplying a hazelcastInstance starts a Hazelcast member that deserializes values read from the backing ReplicatedMap with no class restriction. HazelcastDefaultComponent#getOrCreateHzClientInstance() builds its own ClientConfig when hazelcastMode=client is selected and neither a referenced ClientConfig nor hazelcastConfigUri is supplied, and likewise applied no filter, so client-mode endpoints behaved differently from node-mode endpoints for an otherwise identical configuration. In both cases an attacker able to publish into the Hazelcast cluster that the affected instance is attached to can cause a serialized Java object of their choosing to be deserialized inside Hazelcast's own serialization layer, before Camel processes the exchange, resulting in remote code execution. Hazelcast clusters have neither authentication nor TLS enabled by default. Selecting client mode is a topology choice rather than a security option, so neither path required the deployment to opt in to unsafe behaviour. Users are recommended to upgrade to version 4.23.0, which fixes the issue. If users are on the 4.22.x releases stream, then they are suggested to upgrade to 4.22.1. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.5. The 4.14.x releases stream and earlier reached end of life before this issue was resolved and will not receive a fix, so deployments on those lines must move to a supported release. For deployments that cannot upgrade immediately, supply an explicit Hazelcast configuration carrying a JavaSerializationFilterConfig, or inject a pre-built HazelcastInstance, since a user-supplied configuration is never overwritten by Camel. Alternatively set the JVM-wide filter -Djdk.serialFilter=!java.net.;java.;javax.;org.apache.camel.;!* and enable Hazelcast cluster authentication and TLS to restrict who can reach the cluster.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Apache Software Foundation | Apache Camel | >= 4.0.0, < 4.18.5; >= 4.19.0, < 4.22.1 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-78162?
How severe is CVE-2026-78162?
How do I fix CVE-2026-78162?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-78157A vulnerability was detected in Open5GS 2.8.0. This affects …7.4
- CVE-2026-78158A flaw has been found in Open5GS 2.8.0. This vulnerability a…6.3
- CVE-2026-78159The The Events Calendar plugin for WordPress is vulnerable t…9.8
- CVE-2026-7816OS command injection (CWE-78) vulnerability in pgAdmin 4 Imp…8.8
- CVE-2026-78160A vulnerability has been found in Dolibarr ERP up to 18.0.10…6.3
- CVE-2026-78161A vulnerability was found in warmcat libwebsockets 4.5.0. Im…7.3
- CVE-2026-78163Server-Side Request Forgery (SSRF), Improper Limitation of a…5.9
- CVE-2026-78164Improper Neutralization of Special Elements Used in a Templa…8.2
- CVE-2026-78165Deserialization of Untrusted Data vulnerability in Apache Ca…8.8
- CVE-2026-78166A security flaw has been discovered in provectus kafka-ui up…6.3
- CVE-2026-78167A weakness has been identified in EFM ipTIME T16000M 14.20.2…10
- CVE-2026-78168A security vulnerability has been detected in EFM ipTIME T24…9.8
Are you affected by CVE-2026-78162?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
