cve.bz

CVE-2026-88900 apache camel: Deserialization of Untrusted Data

8.8 highEPSS 0.7%Fix available

High (8.8) in apache camel. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
Deserialization of Untrusted Data vulnerability in Apache Camel Camel-Jgroups component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. JGroupsEndpoint.createExchange(Message), which CamelJGroupsReceiver calls for every message the jgroups consumer receives before the exchange is routed, set the exchange body from org.jgroups.Message.getObject(). For an ObjectMessage, which is the message type the Camel jgroups producer sends, JGroups Java-deserializes the payload through an ObjectInputStream on its own receive thread as the message arrives, and getObject() returns the resulting object. No java.io.ObjectInputFilter was applied on that path unless the deployment had set a JVM-wide serialization filter: camel-jgroups installed none, and the JGroups versions shipped with the affected releases apply none of their own, so any serializable class on the application classpath could be instantiated and its deserialization callbacks run. Unless a channel or the channelProperties option is configured, the consumer creates its channel with new JChannel(), the stock JGroups protocol stack, which multicasts over UDP without the AUTH protocol and without encryption, so any host able to reach the cluster's multicast group or bind port can join the cluster and send messages to the consumer without credentials. Such a host could send a crafted serialized object that leads to remote code execution in the Camel process when a usable deserialization gadget chain is present on the classpath, and no non-default option was required on the consumer. Because JGroups materializes the object before Camel's receiver runs, a check performed by Camel can only inspect the deserialized result and cannot stop code that runs during deserialization, so closing the issue also requires a control that applies before the payload is read, as described in the mitigation. Exploitation requires network access to the cluster's multicast group or bind port, which with the default UDP multicast transport means a host on an adjacent network, and a usable gadget chain on the classpath, which is why the severity is assessed as high rather than critical. 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, and the 4.15.x to 4.17.x and 4.19.x to 4.21.x release lines, 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.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.7% (unchanged from 0.7% a week ago) estimated probability of exploitation activity in the next 30 days; 53rd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-88900 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-88900?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-88900?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-88900 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-88900

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-88900](https://cve.bz/cve/badge/CVE-2026-88900.svg)](https://cve.bz/cve/CVE-2026-88900)

HTML:

<a href="https://cve.bz/cve/CVE-2026-88900"><img src="https://cve.bz/cve/badge/CVE-2026-88900.svg" alt="CVE-2026-88900"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Camelfrom 4.0.0 before 4.18.5
Apache Software Foundation Apache Camelfrom 4.19.0 before 4.22.1

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat Product Security rates this vulnerability as Important because an unauthenticated attacker with adjacent network access can execute arbitrary code within the application runtime. While standard camel-jgroups consumer channels lack transport authentication by default, exploitation requires network reachability to the cluster multicast address or UDP bind port and the presence of exploitable gadget classes on the Java classpath. Workloads that do not utilize camel-jgroups consumer endpoints are not exposed to this issue.

Red Hat's mitigation

--- CME Mitigation Guidance (2026-10-20) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to enforce JVM-wide JEP-290 serialization filters on the Java runtime and require authentication and encryption on JGroups cluster communication channels: upgrade to Apache Camel 4.18.5, 4.22.1, or 4.23.0 (or the fixed Camel Jgroups builds), which filter the deserialized message body type against an ObjectInputFilter allow-list before routing the exchange, closing all 2 injection vectors (crafted serialized object in JGroups ObjectMessage, unauthenticated JGroups cluster membership join). Until patched, this is a concern on deployments running Camel Jgroups consumer channels exposed on an adjacent network, so configure a JVM-wide serialization filter via jdk.serialFilter, enable the AUTH protocol and encryption on JGroups channel configurations, and restrict network access to cluster multicast groups and UDP bind ports. As a compensating measure, deploy EDR agents to detect anomalous process spawning or post-exploitation payloads executed by the Java runtime following gadget chain execution and use Falco or eBPF runtime security to detect suspicious runtime behaviors such as interactive shell execution or abnormal network connections originating from the Camel Java process. These controls limit blast radius and contain exploitation, but they do not fix the underlying unsafe Java deserialization defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-1302 Deserialization Allowlist (Safe Loading) (high)

ProductPackageStateAdvisory
Red Hat Fuse 7camel-jgroupsOut of support scope

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-88900.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

  • oscerd/CVE-2026-88900 Harbor Check: matches CVE 0 stars, Java, created
    Reproducer for CVE-2026-88900 — Apache Camel camel-jgroups unsafe Java deserialization of cluster messages (CWE-502, HIGH). Camel Spring Bo…

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON