dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-4649

MEDIUM · 5.3 CVSS v4.0 Published 2026-03-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Artemis before version 2.52.0 contains an authentication bypass allowing a user with normal privileges and workflow execution capability to register a federated mirror without authentication, enabling unauthorized reading of all internal messages and injection of new messages into the broker.

MitigationUpdate KNIME Business Hub to version 1.18.0, 1.17.4, or 1.16.3 which include the patched Apache Artemis version; no workarounds are available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
Y
User interaction
None
Scope
X

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/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:Y/R:U/V:C/RE:M/U:Amber

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if KNIME Business Hub is installed
    Check for KNIME Business Hub installation directories, services, or installed packages on the system
    Affected if KNIME Business Hub is present on the system and was installed without the patched version of Apache Artemis
  2. Check KNIME Business Hub version
    Look for version information in the KNIME installation directory, about page, or version file (commonly in a VERSION, version.txt, or similar file)
    Affected if The installed version is before 1.16.3, or is between 1.16.3 and 1.17.4 exclusive, or between 1.17.4 and 1.18.0 exclusive (any version before 2.52.0 of the bundled Apache Artemis)
  3. Identify Apache Artemis version bundled with KNIME
    Locate the Apache Artemis installation within the KNIME Business Hub directory structure and check its version file or release artifacts
    Affected if Apache Artemis version is below 2.52.0 (the bundled version is readable in release notes or embedded libraries)
  4. Verify if federated mirror capability is accessible
    Check if the user management or broker configuration interface allows creation or registration of federated mirrors, which requires authenticated access
    Affected if Users with standard privileges can access federated mirror registration without re-authentication or additional verification

The environment is affected if KNIME Business Hub with bundled Apache Artemis below version 2.52.0 is installed and users with standard privileges can register federated mirrors without full authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update KNIME Business Hub to version 1.18.0, 1.17.4, or 1.16.3 which include the patched Apache Artemis version; no workarounds are available.

Recommended fix High confidence

KNIME Business Hub version 1.18.0, 1.17.4, or 1.16.3 (containing fixed Apache Artemis 2.52.0)

  1. Identify the currently installed KNIME Business Hub version
  2. Download the appropriate fixed version (1.18.0, 1.17.4, or 1.16.3) from the official KNIME distribution channels
  3. Follow the standard KNIME Business Hub upgrade documentation for your deployment method
  4. Verify the upgrade was successful by checking the Apache Artemis version bundled with the installation
  5. Test that workflows can execute properly after the upgrade
  6. Confirm the authentication bypass vulnerability is resolved by verifying that federated mirrors now require proper authentication
Caveat Review KNIME upgrade documentation for any version-specific migration requirements; standard upgrade risks apply

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4649 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4649 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data