Live › vulnerability › CVE-2026-115517
Go to dashboardKNIME Business Hub before 1.19.0 does not isolate network access between execution contexts. An authenticated user can reach open ports on executors in other contexts, which matters only if the target IP is known and a workflow has opened a port without authentication.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams running self-hosted KNIME Business Hub with execution contexts where workflows open network ports. Exposure requires an authenticated user who knows the target executor's IP address and a port open without further authentication. Installations on a version of or later, or with manual network policies in place, can skip this.
1.19.0No product ranges from the sources yet.
1.19.0.1.19.0 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Unrestricted network access between execution contexts in KNIME Business Hub before version 1.19.0 allows an authenticated remote user to access open network ports on executors in different execution contexts. This only poses a security issue if the IP address of the attacked executor is know and there are open network ports that provided access without further authentication. By default no network ports are open. However, depending on the running workflows, ports may be opened and provide an attack surface. As a workaround, network policies can be created manually.
This page as .md · .json · in your agent: get_signal("CVE-2026-115517")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.