dbcve.org
Business HubApplication · Knime

CVE-2025-2402

HIGH · 8.6 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 1.10.3 / 1.11.3 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 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
A hard-coded, non-random password for the object store (minio) of KNIME Business Hub in all versions except the ones listed below allows an unauthenticated remote attacker in possession of the password to read and manipulate swapped jobs or read and manipulate in- and output data of active jobs. It is also possible to cause a denial-of-service of most functionality of KNIME Business Hub by writing large amounts of data to the object store directly. There are no viable workarounds therefore we strongly recommend to update to one of the following versions of KNIME Business Hub: * 1.13.2 or later * 1.12.3 or later * 1.11.3 or later * 1.10.3 or later

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

KNIME Business Hub contains a hard-coded, non-random password for its minio object store component across all vulnerable versions. An unauthenticated remote attacker who obtains this password can access the object store to read and manipulate swapped jobs, read/write in/output data of active jobs, and cause denial of service by writing large amounts of data directly to the object store.

MitigationUpdate KNIME Business Hub to version 1.13.2, 1.12.3, 1.11.3, or 1.10.3 or later to remediate this vulnerability; no workarounds are available.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Business HubApplication
Affected:< 1.10.3>= 1.11.0, < 1.11.3>= 1.12.0, < 1.12.3>= 1.13.0, < 1.13.2

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

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. Determine KNIME Business Hub version
    Locate the installed version of KNIME Business Hub through the administration interface, system logs, or product documentation. Common locations include the web-based admin console under system information, or startup logs. Compare the version against: < 1.10.3, >= 1.11.0 and < 1.11.3, >= 1.12.0 and < 1.12.3, >= 1.13.0 and < 1.13.2.
    Affected if The installed version matches any of the listed affected ranges.
  2. Confirm MinIO object store is enabled
    Identify whether the embedded MinIO object store is in use. This is typically the default storage backend for workflow artifacts and job I/O in KNIME Business Hub. Check product documentation or configuration for references to MinIO or S3-compatible storage.
    Affected if The embedded MinIO object store feature is enabled or configured.
  3. Inspect MinIO credential configuration
    Examine the configuration files where MinIO credentials are stored. Look for a hard-coded password value in MinIO-related configuration files or environment settings. The vulnerability exists because a static, non-random password is hard-coded across all unpatched versions.
    Affected if A hard-coded, static password is found in the MinIO configuration rather than a unique, randomly generated credential.

If the installed version falls within the affected ranges and MinIO object store uses the hard-coded credential, the environment is vulnerable to unauthenticated access via CVE-2025-2402.

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
Upgrade available Upgrade to 1.10.3 / 1.11.3 / 1.12.3 or later
Fixed in 1.10.31.11.31.12.3
Interim mitigation

Update KNIME Business Hub to version 1.13.2, 1.12.3, 1.11.3, or 1.10.3 or later to remediate this vulnerability; no workarounds are available.

Recommended fix High confidence

1.13.2 (or 1.12.3, 1.11.3, or 1.10.3 - any of these versions or later)

  1. Backup the current KNIME Business Hub installation and all data including the object store (Minio)
  2. Download the appropriate fixed version of KNIME Business Hub from the official KNIME source (www.knime.com)
  3. Stop the KNIME Business Hub services before upgrading
  4. Install or upgrade to the fixed version (1.13.2, 1.12.3, 1.11.3, or 1.10.3 or later) following the official KNIME upgrade documentation
  5. After upgrade, verify that the hard-coded Minio password has been replaced with a random, secure password
  6. Restart KNIME Business Hub services and verify normal operation

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

Fix this in Business Hub Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2402 — 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-2025-2402 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