---
title: "CVE-2026-78162: Apache Camel - Insecure Deserialization"
description: "Apache Camel 4.0.0 before 4.18.5, 4.19.0 before 4.22.1 contains an insecure deserialization vulnerability caused by missing JavaSerializationFilterConfig in certain Hazelcast configuration paths, letting attackers publishing to the Hazelcast cluster achieve remote code execution, exploit requires attacker to publish malicious serialized objects to the Hazelcast cluster."
url: https://panop.io/threat-heartbeat/CVE-2026-78162/
---

# CVE-2026-78162 Apache Camel - Insecure Deserialization

Apache Camel 4.0.0 before 4.18.5, 4.19.0 before 4.22.1 contains an insecure deserialization vulnerability caused by missing JavaSerializationFilterConfig in certain Hazelcast configuration paths, letting attackers publishing to the Hazelcast cluster achieve remote code execution, exploit requires attacker to publish malicious serialized objects to the Hazelcast cluster.

CVSS base score 10.0 /10

Critical

CISA KEV

Not listed

Public exploit

Proof of concept available

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-78162)

## Details

Type

Insecure Deserialization

Impact

Remote Code Execution

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Published

19 October 2026

Updated

20 October 2026

Weakness

[CWE-502](https://cwe.mitre.org/data/definitions/502.html)

## Vendor fix

Upgrade to Apache Camel version 4.23.0, or 4.22.1 for 4.22.x stream, or 4.18.5 for 4.18.x stream. Alternatively, apply explicit Hazelcast JavaSerializationFilterConfig or enable Hazelcast cluster authentication and TLS.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-78162](https://nvd.nist.gov/vuln/detail/CVE-2026-78162)
- [https://issues.apache.org/jira/browse/CAMEL-24420](https://issues.apache.org/jira/browse/CAMEL-24420)
- [https://camel.apache.org/security/CVE-2026-43865.html](https://camel.apache.org/security/CVE-2026-43865.html)
- [https://camel.apache.org/security/CVE-2026-78162.html](https://camel.apache.org/security/CVE-2026-78162.html)
- [https://github.com/apache/camel/pull/25566](https://github.com/apache/camel/pull/25566)
- [https://github.com/apache/camel/pull/25595](https://github.com/apache/camel/pull/25595)
- [https://github.com/apache/camel/pull/25599](https://github.com/apache/camel/pull/25599)
- [https://github.com/apache/camel/pull/25600](https://github.com/apache/camel/pull/25600)
- [https://issues.apache.org/jira/browse/CAMEL-24413](https://issues.apache.org/jira/browse/CAMEL-24413)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)