CVE-2026-78165
Camel-Spring-Redis default serializer deserializes Redis payloads without a filter, enabling code execution
Apache disclosed CVE-2026-78165 on 15 October 2026. When no serializer is configured, camel-spring-redis reads Redis payloads with Java deserialization and no filter. Anyone able to publish to a subscribed channel can achieve remote code execution, Apache says. Apache CVSS 3.1 8.8. Fixed in 4.18.5, 4.22.1 and 4.23.0. Public reproducer by a Camel PMC member. Not in KEV.
By ThreatWire Desk · Published 19 Oct 2026 · Updated 26 Oct 2026
- CVSS
- 8.8
- Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Class
- RCE
- Status
- PoC Available
- KEV
- Not in CISA KEV
- 0-day
- No
- Vendor
- Apache
- Products
- Apache Camel, camel-spring-redis
- Affected
- Apache Camel (org.apache.camel:camel-spring-redis) from 2.11.0 before 4.18.5, and from 4.19.0 before 4.22.1. The 4.14.x line and older are end of life and get no fix.
- Fixed
- Apache Camel 4.18.5 (4.18.x LTS), 4.22.1 (4.22.x) and 4.23.0.
- CWE
- CWE-502
- Published
- 19 Oct 2026
- Updated
- 26 Oct 2026
The status above is the claim. Links do not upgrade it.
CVE-2026-78165 is an unsafe Java deserialization flaw in camel-spring-redis, the Apache Camel component for Redis through Spring Data. Apache published the advisory on 15 October 2026. The CVE record and NVD entry followed on 19 October.
When no serializer option is set, the component builds Spring's JDK serialization serializer. That serializer installs no deserialization filter.
The consumer applies it to every message on the subscribed channels, before any route logic runs. An actor who can publish to a subscribed channel reaches the sink directly. Apache says this allows remote code execution.
The same default also covers producer reads (GET, HGET, HGETALL, HVALS) and the Redis idempotent repository. Setting a custom template does not close the consumer path. Only the serializer option does.
The attacker needs the right to publish on the Redis instance. That is why Apache's score assumes low privileges. A Redis server without authentication lowers that bar.
Apache scores it CVSS 3.1 8.8 (High). NVD shows the Apache score and has not added its own.
Affected: 2.11.0 before 4.18.5, and 4.19.0 before 4.22.1. The behaviour dates back to the first release of the component. Fixed: 4.18.5, 4.22.1 and 4.23.0. The 4.14.x line is end of life.
The fix adds a default allow-list filter and a new deserializationFilter option. Before you can upgrade, Apache suggests a JVM-wide serialization filter, or a serializer that does not use Java serialization, set on the serializer option itself.
The advisory credits Leon Zlobecki. A public reproducer repository is published by Andrea Cosentino (oscerd), the Camel PMC member who wrote the fix. CISA's SSVC entry tags it as a PoC. ThreatWire did not run it and does not reprint its content.
The CVE is not in the CISA KEV catalog (catalog 2026.10.23). No exploitation in the wild is reported.
Read the full explainer on the eight Camel and Camel K flaws. The JGroups flaw CVE-2026-88900 belongs to the same family.
Sources
Related on ThreatWire
- NewsApache Camel and Camel K: eight high and critical flaws, from OAuth bypass to deserialization RCE
- VendorAll Apache CVEs in the ThreatWire tracker
- CVE recordCVE-2026-88900: Camel-JGroups consumer deserializes cluster messages without a filter, leading to code execution
- CVE recordCVE-2026-78164: Camel HTTP producers resolve property placeholders in message-supplied URI headers, exposing secrets
- CVE recordCVE-2026-80312: Camel-OAuth processors fail open, letting requests that failed authentication through
- CVE recordCVE-2026-85251: Camel-HTTP re-sends credentials to whatever host a redirect names
- CVE recordCVE-2026-88901: Camel-Smooks resolves external XML entities by default, allowing local file reads
- CVE recordCVE-2026-88789: Camel Quarkus Xalan TransformerFactory drops XXE hardening