Skip to main content
VulnerabilityPublished

CVE-2026-4649: KNIME Business Hub · Missing Authentication

Affects KNIME Business HubSource CVE Database V5

0
Compare

Mentioned vulnerabilities

Not known to be exploited · CVSS 5.3 Medium · fixed in 1.17.4 : update KNIME Business Hub when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.17.4, 1.16.3, 1.15.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/AU:Y/R:U/V:C/RE:M/U:Amber

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade KNIME Business Hub to 1.17.4, 1.16.3 or 1.15.2.

Affected software

ProductAffectedFixed in
KNIMEKNIME Business HubAffected
  • >=1.17.0 <1.17.4
Fixed in
  • 1.17.4
KNIMEKNIME Business HubAffected
  • >=1.16.0 <1.16.3
Fixed in
  • 1.16.3
KNIMEKNIME Business HubAffected
  • <1.15.2
Fixed in
  • 1.15.2
Mavencom.knime/business-hubpkg:maven/com.knime/business-hubOther threatsAffected
  • =1.17.0
  • =1.16.0
  • =0.0.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately upgrade KNIME Business Hub to versions 1.16.3, 1.17.4, 1.18.0 or later, which include the patched Apache Artemis 2.52.0.
  2. Restrict workflow execution privileges strictly to trusted users to minimize the risk of exploitation by insiders or compromised accounts.
  3. Implement strong internal access controls and monitoring to detect unusual federated mirror registrations or message injection attempts within the Artemis broker.
  4. Audit user permissions regularly to ensure least privilege principles are enforced, especially for users with workflow execution capabilities.
  5. Consider network segmentation to isolate the Artemis broker and limit access to only necessary components and users.
  6. Monitor logs and alerts for signs of unauthorized message reading or injection activities.
  7. Engage with KNIME support or security advisories for any emerging mitigations or patches. Since no workaround exists, patching remains the primary defense.

Description

Apache Artemis before version 2.52.0 is affected by an authentication bypass flaw which allows reading all messages exchanged via the broker and injection of new message ( CVE-2026-27446 https://www.cve.org/CVERecord ). Since KNIME Business Hub uses Apache Artemis it is also affected by the issue. However, since Apache Artemis is not exposed to the outside it requires at least normal user privileges and the ability to execute workflows in an executor. Such a user can install and register a federated mirror without authentication to the original Apache Artemis instance and thereby read all internal messages and inject new messages. The issue affects all versions of KNIME Business Hub. A fixed version of Apache Artemis is shipped with versions 1.18.0, 1.17.4, and 1.16.3. We recommend updating to a fixed version as soon as possible since no workaround is known.

References

Community reviews

Loading reviews…