Quick answers
- Is CVE-2026-63619 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63619 being exploited in the wild.
- How severe is CVE-2026-63619?
- 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-63619?
- 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-63619 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-63619?
- 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 backend metadata dump API in Apache Kylin fails to enforce sufficient authorization checks and lacks proper path-confinement controls. An attacker with network access to the API can request sensitive metadata dumps without authentication or authorization verification, potentially exposing configuration and system information. A fix is available in version 5.0.5.
Affected products
- Apache Kylin 4.0.0 through 5.0.4
Timeline
- 2026-10-16: disclosed
- 2026-10-16: patched: version 5.0.5 released