# CVE-2026-4649: Auth bypass in Apache Artemis allows reading all internal messages

> Authenticated users can bypass authentication to read and inject internal messages in KNIME Business Hub via Apache Artemis.

- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Mar 2026
- **Updated:** 24 Mar 2026
- **Also known as:** GHSA-c27m-9j97-3ghp, UBUNTU-CVE-2026-4649

## What is CVE-2026-4649?

CVE-2026-4649 is a medium-severity authentication bypass vulnerability in KNIME Business Hub, published on 24 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-4649?


## How do I fix CVE-2026-4649?

No fix has been published for CVE-2026-4649 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-4649 being exploited?

There is no known exploitation of CVE-2026-4649 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4649 and fix it if it is affected.

What it is: CVE-2026-4649 is a medium-severity authentication bypass vulnerability in KNIME Business Hub, published on 24 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-4649 in the wild and no public exploit code.

Affected product: KNIME Business Hub. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-4649/ (Markdown: https://insights.sbomify.com/CVE-2026-4649/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4649
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4649
- OSV: https://osv.dev/vulnerability/CVE-2026-4649

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-4649/
Summaries are generated and may contain mistakes; the official description above is the record.