{"id":"CVE-2026-115517","kind":"vulnerability","aliases":["CVE-2026-115517"],"related":[],"title":"KNIME Business Hub: unrestricted network access between execution contexts","description":"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.","summary":"KNIME 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.","severity":"medium","cvss":6.4,"epss":0.00431,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["knime","kubernetes","other","self-hosted"],"not_affected_if":["no-open-executor-ports","version-1.19.0-or-later"],"how_to_check":"- Check the KNIME Business Hub version in the installation; affected versions are those before `1.19.0`.\n- Review whether network policies restrict traffic between execution contexts (unknown whether the sources list a specific command or setting).","fix":"- Upgrade KNIME Business Hub to `1.19.0` or later.\n- Until upgraded, create network policies manually to block traffic between execution contexts, as the advisory suggests.","status":"open","published_at":"2026-10-22T19:17:48+00:00","first_seen_at":"2026-10-23T21:57:31+00:00","triaged_at":"2026-10-25T03:59:15+00:00","updated_at":"2026-10-25T03:59:15+00:00","category":"other","confidence":0.7,"triage":{"at":"2026-10-25T03:59:15Z","model":"claude-haiku-5-5","output":{"fix":"- Upgrade KNIME Business Hub to `1.19.0` or later.\n- Until upgraded, create network policies manually to block traffic between execution contexts, as the advisory suggests.","reach":"network","title":"KNIME Business Hub: unrestricted network access between execution contexts","impact":"medium","summary":"KNIME 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.","category":"other","nicknames":[],"who_cares":["knime","self-hosted","kubernetes"],"confidence":0.7,"needs_auth":"yes","worst_case":"Authenticated user reaches unauthenticated ports on other executors","analyst_note":"","how_to_check":"- Check the KNIME Business Hub version in the installation; affected versions are those before `1.19.0`.\n- Review whether network policies restrict traffic between execution contexts (unknown whether the sources list a specific command or setting).","needs_analyst":false,"not_affected_if":["version-1.19.0-or-later","no-open-executor-ports"],"who_is_affected":"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 `1.19.0` or later, or with manual network policies in place, can skip this.","user_interaction":"no","needs_special_setup":"yes","severity_if_unknown":"medium"},"cost_usd":0.000616,"input_tokens":3406,"output_tokens":551,"severity_before":"medium"},"analyst_status":null,"analyst_note":null,"search":"'-115517':12A,15A '-2026':11A,14A '1.19.0':26B,77C 'access':6A,31B,67C,84C,118C 'address':103C 'allow':78C 'attack':106C,142C 'authent':36B,64B,80C,121C 'busi':2A,23B,73C 'context':9A,34B,46B,70C,93C 'creat':151C 'cve':10A,13A 'default':123C 'depend':130C 'differ':91C 'execut':8A,33B,69C,92C 'executor':43B,89C,107C 'host':21B 'howev':129C 'hub':3A,24B,74C 'ip':53B,102C 'isol':29B 'issu':99C 'knime':1A,16B,22B,72C 'know':109C 'known':55B 'kubernet':17B 'manual':152C 'matter':48B 'may':136C 'network':5A,30B,66C,86C,114C,125C,147C 'open':40B,60B,85C,113C,128C,138C 'polici':148C 'port':41B,62B,87C,115C,126C,135C 'pose':96C 'provid':117C,140C 'reach':39B 'remot':81C 'run':133C 'secur':98C 'self':20B 'self-host':19B 'surfac':143C 'target':52B 'unrestrict':4A,65C 'user':37B,82C 'version':76C 'without':63B,119C 'workaround':146C 'workflow':58B,134C","nicknames":[],"mitigations":[],"who_affected":"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 `1.19.0` or later, or with manual network policies in place, can skip this.","tier":"C","verified":{},"analyst_revisit_at":null,"first_public_at":"2026-10-22T19:17:48+00:00","kev":null,"cvss_vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","cvss_by":"security@knime.com","poc_count":0,"sources":[{"source":"nvd","external_id":"CVE-2026-115517","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-115517","severity":null,"published_at":"2026-10-22T19:17:48+00:00","modified_at":"2026-10-23T19:43:46+00:00","first_seen_at":"2026-10-23T21:57:31+00:00","fetched_at":"2026-10-23T22:29:02+00:00","note":null},{"source":"epss","external_id":"CVE-2026-115517","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-115517","severity":null,"published_at":null,"modified_at":null,"first_seen_at":"2026-10-24T07:15:51+00:00","fetched_at":"2026-10-24T07:15:51+00:00","note":null}],"documents":[],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}