KNIME Documentation

KNIME Business Hub 1.11 Release Notes ​

KNIME Business Hub 1.11.4 ​

(released March 28, 2025)

Security fix ​

This release resolves a security vulnerability in all prior versions of KNIME Business Hub.

On March 24, 2025, a high-severity vulnerability in the widely used ingress-nginx component for Kubernetes was publicly disclosed. By sending specially crafted HTTP requests from within the cluster to the ingress-nginx controller, attackers could achieve remote code execution. Since ingress-nginx holds access to all cluster credentials, this vulnerability could lead to a full cluster takeover.

For full details, refer to the KNIME Security Advisory: CVE-2025-2787.

KNIME Business Hub 1.11.3 ​

(released March 20, 2025)

Security fix ​

This release addresses a security vulnerability affecting all previous versions of KNIME Business Hub. We’ve identified that the existing Kubernetes secret configuration could potentially allow parties with specific credential knowledge to interact with job-related data on accessible KNIME Business Hub installations.

For more details, see the KNIME Security Advisory: CVE-2025-2402.

KNIME Business Hub 1.11.2 ​

(released August 21, 2024)

Important installation notes ​

  • Updates from the Business Hub 1.11.x version are highly recommended, as critical issues were fixed in this release.

Important bug fixes ​

  • Fixed an issue in SCIM integration where percentage-encoding did not allow upper- and lowercase characters in SCIM endpoints
  • Fixed a bug where "number of executors" setting didn’t work for shared execution contexts through the Business Hub UI
  • Fixed an issue where refreshing a Box/Generic/Google OAuth2 Interactive secret via the Secret Store consume endpoint failed on the second refresh
  • Fixed an issue where Keycloak didn’t start up properly in some cases after a restart
  • Fixed an issue in Secret Store where Google Sheets (read-only) scope group contained invalid scopes

Infrastructure update ​

  • Security update: KNIME Business Hub does no longer utilize role bindings to default service accounts

KNIME Business Hub 1.11.1 ​

(released August 9, 2024)

Important installation notes ​

  • Updates from the Business Hub 1.11.0 version are highly recommended, as critical issues were fixed in this release.
  • Important If an external loadbalancer is deployed for handling TLS, and the coreDNS configuration update is disabled, the checkbox Istio Outbound Traffic Redirect has to be disabled as well. Otherwise, internal calls to the hub URL will skip the Loadbalancer and TLS is not handled.

Important bug fix ​

  • Fixed the issue where in Business Hub 1.11.0 discarding and swapping jobs from running executors were not happening automatically. This would result in jobs piling up on the executor causing critical problems.

KNIME Business Hub 1.11.0 ​

(released July 24, 2024)

Important installation notes ​

Important: If an external Loadbalancer is deployed for handling TLS, and the CoreDNS configuration update is disabled, the checkbox "Istio Outbound Traffic Redirect" has to be disabled as well on the KOTS Admin Console. Otherwise, internal calls to the Hub URL will skip the Loadbalancer and TLS is not handled.

Notice that due to the Postgres database update ~10 minutes downtime is expected.

Improvements ​

  • KNIME Business Hub now provides a GenAI Gateway that allows IT to centrally configure which GenAI providers and nodes can be accessed and used by team members
  • Workflows and components now come with rich descriptions
  • Personal credentials are now available to logged-in read-only users
  • Admins of KNIME Business Hub can assign memory limits to Teams

Infrastructure updates ​

  • Postgres database has been updated to version 16
  • Artemis has been updated to version 2.35.0
  • Quarkus has been updated to version 3.8 LTS

Important bug fixes ​

  • Fixed an issue where members of a Team could see the delete button for Deployments even if they didn’t have the permission to delete them
  • Fixed an issue where deployment of Kots failed when there was no TLS certificate defined
  • Security context fixes
  • Various small bug fixes