Quick answers
- Is CVE-2026-108743 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-108743 being exploited in the wild.
- How severe is CVE-2026-108743?
- Informational severity, published 16 October 2026.
- Which products and versions are affected?
- Apache Kylin 4.0.4 through 5.0.4.
- Is there a fix for CVE-2026-108743?
- Yes: fixed in 5.0.5. Until then: Avoid exposing Kylin services directly to public networks; deploy Kylin only in protected in-house environments or behind network access controls that restrict exposure to trusted networks only. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-108743 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-108743?
- 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
Avoid exposing Kylin services directly to public networks; deploy Kylin only in protected in-house environments or behind network access controls that restrict exposure to trusted networks only.
Technical details
The vulnerability is an improper neutralization of special elements in an OS command, allowing command injection attacks. It affects Kylin versions 4.0.4 through 5.0.4 when services are directly exposed to untrusted networks. An unauthenticated network attacker can inject OS commands and execute arbitrary code with the privileges of the Kylin service.
Affected products
- Apache Kylin 4.0.4 through 5.0.4
Timeline
- 2026-10-16: disclosed