Quick answers
- Is CVE-2026-108780 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-108780 being exploited in the wild.
- How severe is CVE-2026-108780?
- Informational severity, published 19 October 2026.
- Which products and versions are affected?
- Apache Kylin 4.0.0 through 5.0.4.
- Is there a fix for CVE-2026-108780?
- Yes: fixed in 5.0.5. Until then: Restrict network access to Kylin backend services and ensure they are not directly exposed to public or untrusted networks until the upgrade can be applied. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-108780 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-108780?
- 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
Restrict network access to Kylin backend services and ensure they are not directly exposed to public or untrusted networks until the upgrade can be applied.
Technical details
A configuration validation vulnerability exists in Kylin's JDBC source handling that fails to properly validate source configurations. The vulnerability requires either network access to exposed backend services or prior authentication. Successful exploitation could disclose or modify database connection credentials stored in Kylin's configuration. A fix is available in version 5.0.5 and later.
Affected products
- Apache Kylin 4.0.0 through 5.0.4
Timeline
- 2026-10-19: disclosed