CVSS 3.1
8.8 highCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HHigh (8.8) in apache camel. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExplain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Apache Software Foundation Apache Camel | from 4.0.0 before 4.18.5 |
| Apache Software Foundation Apache Camel | from 4.19.0 before 4.22.1 |
Red Hat rates this Important.
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.
--- 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)
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Fuse 7 | camel-jgroups | Out 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.
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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.