CVE-2026-64610: Apache Kylin unsafe deserialization in external cache

CVE-2026-64610 · Severity: info · Published 2026-10-16

Apache Kylin, an analytics platform, contains a vulnerability that allows unsafe Java deserialization when communicating with an external cache service like Redis. An attacker could exploit this through a compromised or malicious cache service to execute arbitrary code on the Kylin server, potentially leading to data theft or system compromise.

Technologies: Apache Kylin. Vendors: Apache.

Quick answers

Is CVE-2026-64610 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-64610 being exploited in the wild.
How severe is CVE-2026-64610?
Informational severity, published 16 October 2026.
Which products and versions are affected?
Apache Kylin 4.0.0 through 5.0.4.
Is there a fix for CVE-2026-64610?
Yes: fixed in 5.0.5. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-64610 attacked?
It is attacked over the network.
Am I affected by CVE-2026-64610?
Check whether you run Apache Kylin at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 5.0.5

Technical details

The vulnerability stems from unsafe Java deserialization of untrusted data received from an external cache service. This can occur when the cache service is broken or malicious, allowing an attacker to inject crafted serialized Java objects. Exploitation requires network access to the Kylin instance or control over the external cache service.

Affected products

  • Apache Kylin 4.0.0 through 5.0.4

Timeline

  • 2026-10-16: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.