cve.bz

CVE-2026-78165 apache software foundation apache camel: Deserialization of Untrusted Data

8.8 highEPSS 0.7%

High (8.8) in apache software foundation 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 Spring Redis component. This issue affects Apache Camel: from 2.11.0 before 4.18.5, from 4.19.0 before 4.22.1. RedisConfiguration.getSerializer lazily built a bare JdkSerializationRedisSerializer whenever no serializer option was configured, and that instance was used for every read the component performs. Spring's implementation delegates through DeserializingConverter to DefaultDeserializer, which reads the bytes with a ConfigurableObjectInputStream and installs no java.io.ObjectInputFilter on the stream, so an arbitrary serialized class graph was materialised and its readObject method executed. RedisConsumer.setBody applied that serializer to the raw bytes of every message published to the subscribed channels, before the Exchange was constructed and therefore before any route logic could inspect the message, so an actor able to issue PUBLISH on a subscribed channel reached the deserialization sink directly. The same default serializer backed the RedisTemplate built by RedisConfiguration.createDefaultTemplate, so the producer read commands GET, HGET, HGETALL and HVALS deserialized whatever was stored in the Redis keyspace, and SpringRedisIdempotentRepository shared that template. Configuring a custom redisTemplate did not close the consumer path, because RedisConsumer.setBody reads getSerializer directly rather than the serializer attached to the template, so a deployment that had wired a String serializer into its own template remained exposed on the consumer side unless it also set the serializer option. The component never constructed a java.io.ObjectInputStream itself, which is why earlier passes over the Camel codebase for unfiltered Java deserialization did not reach it. The behaviour dates back to the introduction of the component, first released in 2.11.0, and was unchanged until this fix. 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 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. For deployments that cannot upgrade immediately, set the JVM-wide jdk.serialFilter system property, which the affected code path honours because it reads through a java.io.ObjectInputStream, for example -Djdk.serialFilter=!java.net.**;java.**;javax.**;org.apache.camel.**;!* ; or set the serializer endpoint option to a serializer that does not use Java serialization, such as StringRedisSerializer, noting that this must be set as the serializer option and not only on a custom redisTemplate. As defence in depth, require authentication on the Redis instance and restrict which clients may publish to the subscribed channels, and do not expose a Redis instance consumed by Camel to untrusted networks.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/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; 55th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-10-20. 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
Under analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain 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.

Affected

  • apache software foundation:apache camel

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Camelfrom 2.11.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

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.

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

ProductPackageStateAdvisory
Red Hat build of Apache Camel for Spring Boot 4camel-spring-redisAffected
Red Hat Fuse 7camel-spring-redisAffected

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.

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. How Harbor Check reads them, and what it found.

  • oscerd/CVE-2026-78165 Harbor Check: matches CVE 0 stars, Java, created
    Reproducer for CVE-2026-78165 (Apache Camel camel-spring-redis): default JdkSerializationRedisSerializer deserializes Redis PUBLISH payload…

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