---
title: "CVE-2026-88900: Apache Camel Camel-Jgroups - Insecure Deserialization"
description: "Apache Camel Camel-Jgroups 4.0.0 < 4.18.5, 4.19.0 < 4.22.1 contains an insecure deserialization vulnerability caused by unfiltered Java deserialization of JGroups messages, letting attackers with network access to multicast group execute arbitrary code remotely, exploit requires network access to cluster multicast or bind port and a usable deserialization gadget chain."
url: https://panop.io/threat-heartbeat/CVE-2026-88900/
---

# CVE-2026-88900 Apache Camel Camel-Jgroups - Insecure Deserialization

Apache Camel Camel-Jgroups 4.0.0 < 4.18.5, 4.19.0 < 4.22.1 contains an insecure deserialization vulnerability caused by unfiltered Java deserialization of JGroups messages, letting attackers with network access to multicast group execute arbitrary code remotely, exploit requires network access to cluster multicast or bind port and a usable deserialization gadget chain.

CVSS base score 8.8 /10

High

CISA KEV

Not listed

Public exploit

None known

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

## Details

Type

Insecure Deserialization

Impact

Remote Code Execution

CVSS vector

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Published

19 October 2026

Updated

20 October 2026

Weakness

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

## Vendor fix

Upgrade to version 4.23.0, or 4.22.1 for 4.22.x stream, or 4.18.5 for 4.18.x stream.

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-88900](https://nvd.nist.gov/vuln/detail/CVE-2026-88900)
- [https://issues.apache.org/jira/browse/CAMEL-25223](https://issues.apache.org/jira/browse/CAMEL-25223)
- [https://camel.apache.org/security/CVE-2026-40860.html](https://camel.apache.org/security/CVE-2026-40860.html)
- [https://camel.apache.org/security/CVE-2026-88900.html](https://camel.apache.org/security/CVE-2026-88900.html)
- [https://github.com/apache/camel/pull/26267](https://github.com/apache/camel/pull/26267)
- [https://github.com/apache/camel/pull/26281](https://github.com/apache/camel/pull/26281)
- [https://github.com/apache/camel/pull/26282](https://github.com/apache/camel/pull/26282)
- [https://github.com/apache/camel/pull/27205](https://github.com/apache/camel/pull/27205)
- [https://issues.apache.org/jira/browse/CAMEL-24676](https://issues.apache.org/jira/browse/CAMEL-24676)
- [https://github.com/apache/camel/pull/26283](https://github.com/apache/camel/pull/26283)
- [https://github.com/apache/camel/pull/26326](https://github.com/apache/camel/pull/26326)

[← 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)
