Quick answers
- Is CVE-2026-69080 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-69080 being exploited in the wild.
- How severe is CVE-2026-69080?
- Informational severity, published 16 October 2026.
- Which products and versions are affected?
- Apache Kylin 4 through 5.0.4.
- Is there a fix for CVE-2026-69080?
- 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-69080 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-69080?
- 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
A SQL blacklist exposure vulnerability in Apache Kylin allows unauthorized actors to view the SQL blacklist configuration that should be restricted. The issue affects versions 4 through 5.0.4 and requires network access to the Kylin instance. An attacker with unauthenticated or low-privilege access can disclose the blacklist policies used to restrict dangerous queries.
Affected products
- Apache Kylin 4 through 5.0.4
Timeline
- 2026-10-16: disclosed