Quick answers
- Is CVE-2026-115517 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115517 being exploited in the wild.
- How severe is CVE-2026-115517?
- Informational severity, published 22 October 2026.
- Which products and versions are affected?
- Knime Business Hub before 1.19.0.
- Is there a fix for CVE-2026-115517?
- Yes: fixed in KNIME Business Hub 1.19.0. Until then: Network policies can be created manually to restrict communication between execution contexts and control outbound access from executors. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-115517 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-115517?
- Check whether you run Knime Business Hub 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: KNIME Business Hub 1.19.0
Network policies can be created manually to restrict communication between execution contexts and control outbound access from executors.
Technical details
An authorization or isolation flaw in KNIME Business Hub before 1.19.0 permits authenticated users to initiate network connections to executors in different execution contexts without proper isolation controls. The attack requires knowledge of the target executor's IP address and the presence of open network ports; by default no ports are exposed. The vulnerability allows lateral movement within the platform's infrastructure if workflows running in other contexts open network services.
Affected products
- KNIME Business Hub before 1.19.0
Timeline
- 2026-10-22: disclosed