CVSS 3.1
8.8 highCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HHigh (8.8) in apache software foundation apache camel. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExplain CVE-2026-78165 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-78165?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-78165?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-78165 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 2.11.0 before 4.18.5 |
| Apache Software Foundation Apache Camel | from 4.19.0 before 4.22.1 |
Red Hat rates this Important.
This vulnerability is rated as an Important severity impact because successful exploitation can lead to arbitrary code execution within the context of the running application process. Although network-accessible without user interaction, exploitation requires an attacker to possess network reachability and sufficient authorization to write data or publish messages directly to the underlying Redis instance monitored by the application. Consequently, deployments where the Redis instance is strictly isolated and access-controlled face reduced practical risk.
--- 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 eliminate unfiltered Java deserialization across camel-spring-redis consumers, producer reads, and idempotent repositories by enforcing ObjectInputFilter validation or configuring non-Java serializers: upgrade to Apache Camel 4.18.5, 4.22.1, or 4.23.0 (or the fixed Camel Spring Redis builds), which enforce an ObjectInputFilter using a custom FilteringDeserializer and configurable deserialization filter options during deserialization, closing all 3 injection vectors (publishing crafted serialized Java payloads to subscribed Redis channels, writing crafted serialized Java payloads to Redis keys read by producer commands, populating crafted serialized Java payloads in keys queried by SpringRedisIdempotentRepository). Until patched, this is a concern on deployments running Camel Spring Redis routes without a custom non-Java serializer option, so set the JVM-wide jdk.serialFilter property, configure the endpoint serializer option to a non-Java serializer such as StringRedisSerializer, and enforce authentication while restricting network write and publish access to Redis. As a compensating measure, deploy EDR agents to detect anomalous process execution and malicious payload activity spawned from the Java process following deserialization and configure Falco or eBPF runtime security monitoring to detect unexpected shell executions or outbound network connections originating from the Camel application. These controls limit blast radius and contain exploitation, but they do not fix the underlying untrusted 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 build of Apache Camel for Spring Boot 4 | camel-spring-redis | Affected | |
| Red Hat Fuse 7 | camel-spring-redis | Affected |
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-78165.
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. How Harbor Check reads them, and what it found.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.