CVE-2026-4649: Auth bypass in Apache Artemis allows reading all internal messages
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-4649?
CVE-2026-4649 has been classified as a high severity vulnerability due to the potential for unauthorized message access and injection.
How do I fix CVE-2026-4649?
To fix CVE-2026-4649, upgrade Apache Artemis to version 2.52.0 or later to mitigate the authentication bypass issue.
What software is affected by CVE-2026-4649?
CVE-2026-4649 affects Apache Artemis versions prior to 2.52.0 and may impact KNIME Business Hub indirectly.
What are the risks associated with CVE-2026-4649?
The risks associated with CVE-2026-4649 include unauthorized access to sensitive messages and the ability to inject malicious messages.
Is there a workaround for CVE-2026-4649 if I cannot upgrade?
Currently, there are no known workarounds for CVE-2026-4649; upgrading to a patched version is strongly recommended.