PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-78165 Apache Software Foundation CVE debrief

The Apache Camel Spring Redis component is vulnerable to Deserialization of Untrusted Data. This high-severity issue affects Apache Camel versions from 2.11.0 before 4.18.5 and from 4.19.0 before 4.22.1, allowing an attacker to execute arbitrary code by deserializing untrusted data. Defenders and developers using this component should assess exposure, prioritize remediation, and implement compensating controls. The vulnerability is due to the RedisConfiguration.getSerializer lazily building a bare JdkSerializationRedisSerializer, which is used for every read the component performs, leading to arbitrary serialized class graph materialization and execution of its readObject method.

Vendor
Apache Software Foundation
Product
Apache Camel
CVSS
HIGH 8.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-19
Original CVE updated
2026-10-20
Advisory published
2026-10-19
Advisory updated
2026-10-20

Who should care

Defenders and developers using Apache Camel Spring Redis component should assess exposure and prioritize remediation. This vulnerability requires verification of affected versions, inventory checks, and compensating controls.

Why it matters

CVE-2026-78165 is a high-severity vulnerability in Apache Camel Spring Redis component that allows deserialization of untrusted data, potentially leading to arbitrary code execution. Defenders and developers should assess exposure, prioritize remediation, and implement compensating controls.

  • Verify affected Apache Camel versions and upgrade to fixed versions
  • Implement jdk.serialFilter system property to restrict deserialization
  • Configure custom serializer endpoint options to prevent arbitrary code execution
  • Restrict publishing to subscribed Redis channels and require authentication

Technical summary

The Apache Camel Spring Redis component has a Deserialization of Untrusted Data vulnerability. This issue affects Apache Camel versions from 2.11.0 before 4.18.5 and from 4.19.0 before 4.22.1. The vulnerability allows an attacker to execute arbitrary code by deserializing untrusted data. The issue arises from RedisConfiguration.getSerializer lazily building a bare JdkSerializationRedisSerializer, which is used for every read the component performs. This leads to arbitrary serialized class graph materialization and execution of its readObject method. Users can mitigate this by setting the JVM-wide jdk.serialFilter system property or configuring a custom serializer endpoint option.

Defensive priority

High

Recommended defensive actions

  • Upgrade to Apache Camel version 4.23.0 or later
  • Set the JVM-wide jdk.serialFilter system property
  • Configure a custom serializer endpoint option
  • Require authentication on the Redis instance and restrict publishing to subscribed channels
  • Verify affected Apache Camel versions and upgrade to fixed versions
  • Implement compensating controls for exposed systems while remediation is scheduled and verified
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details on the Deserialization of Untrusted Data vulnerability in Apache Camel Spring Redis component. The issue affects Apache Camel versions from 2.11.0 before 4.18.5 and from 4.19.0 before 4.22.1.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-78165 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-78165

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-78165 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-78165

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.