Vulnerability/
https://seclists.org/oss-sec/2026/q4/180

https://seclists.org/oss-sec/2026/q4/180: CVE-2026-68571: Apache Kylin: JDBC URL Whitelist Verification Bypass

Q: Which deployments are most exposed to this issue?

Apache Kylin services directly exposed to the public network are most affected. The advisory states that this is uncommon and that most in-house Kylin deployments are not impacted.

Q: What does an attacker need to exploit the vulnerability?

The issue is triggered through a special parameter in a JDBC URL that bypasses whitelist verification and can lead to code injection. The advisory does not specify any additional authentication or access prerequisites.

Q: What versions should be remediated, and what is the fix?

Apache Kylin versions 4.0.0 through 5.0.4 are affected. Upgrade to version 5.0.5, which fixes the issue.

Published Oct 16, 2026

Updated

Affected Software

1 affected component

Apache Kylin>=4.0.0<=5.0.4

Frequently Asked Questions

Which deployments are most exposed to this issue?

Apache Kylin services directly exposed to the public network are most affected. The advisory states that this is uncommon and that most in-house Kylin deployments are not impacted.

What does an attacker need to exploit the vulnerability?

The issue is triggered through a special parameter in a JDBC URL that bypasses whitelist verification and can lead to code injection. The advisory does not specify any additional authentication or access prerequisites.

What versions should be remediated, and what is the fix?

Apache Kylin versions 4.0.0 through 5.0.4 are affected. Upgrade to version 5.0.5, which fixes the issue.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.