dbcve.org
Business HubApplication · Knime

CVE-2025-2787

HIGH · 8.8 CVSS v3.1 Published 2025-03-26
Fix available
A fix is available. Upgrade to 1.10.4 / 1.11.4 or later.
See remediation →
94/100
Remediation priority · Urgent
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
KNIME Business Hub is affected by the Ingress-nginx CVE-2025-1974 ( a.k.a IngressNightmare ) vulnerability which affects the ingress-nginx component. In the worst case a complete takeover of the Kubernetes cluster is possible. Since the affected component is only reachable from within the cluster, i.e. requires an authenticated user, the severity in the context of KNIME Business Hub is slightly lower. Besides applying the publicly known workarounds, we strongly recommend updating to one of the following versions of KNIME Business Hub: * 1.13.3 or above * 1.12.4 or above * 1.11.4 or above * 1.10.4 or above *

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 vulnerable version of the ingress-nginx controller affected by CVE-2025-1974 (IngressNightmare). This vulnerability allows remote code execution or complete Kubernetes cluster takeover in worst-case scenarios. While the ingress-nginx component is only accessible from within the cluster and requires authenticated user access, the high CVSS score (8.8) reflects the severe impact if exploited.

MitigationUpdate KNIME Business Hub to version 1.13.3, 1.12.4, 1.11.4, or 1.10.4 or above to patch the ingress-nginx component vulnerability. Alternatively, apply publicly documented workarounds for CVE-2025-1974.

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.0, < 1.10.4>= 1.11.0, < 1.11.4>= 1.12.0, < 1.12.4>= 1.13.0, < 1.13.3

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Identify KNIME Business Hub installed version
    Check the product version through the administration interface under 'About' or by querying the Kubernetes deployment: kubectl get deployment -n <knime-namespace> -o jsonpath='{.items[*].spec.template.spec.containers[*].env[?(@.name=="PRODUCT_VERSION")].value}'
    Affected if The version falls within any of these ranges: >=1.10.0 and <1.10.4, >=1.11.0 and <1.11.4, >=1.12.0 and <1.12.4, or >=1.13.0 and <1.13.3
  2. Locate ingress-nginx controller in the cluster
    Run: kubectl get pods -n ingress-nginx -o wide or kubectl get pods -n <knime-namespace> | grep ingress
    Affected if An ingress-nginx controller pod exists in the cluster (either in ingress-nginx namespace or the Knime namespace)
  3. Check ingress-nginx controller image version
    Run: kubectl get pods -n ingress-nginx -o jsonpath='{.items[*].spec.containers[*].image}' or kubectl get deployment ingress-nginx-controller -n ingress-nginx -o jsonpath='{.spec.template.spec.containers[*].image}'
    Affected if The image version is older than the patched version (v1.11.0 or later for CVE-2025-1974)
  4. Verify ingress-nginx admission webhook configuration
    Run: kubectl get validatingwebhookconfigurations ingress-nginx-admission -o yaml and check if the webhook is exposed without proper network policies
    Affected if The admission webhook is accessible from within the cluster without strict network isolation

You are affected if KNIME Business Hub version is below the fixed versions AND an ingress-nginx controller with a vulnerable version is present in your cluster.

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.4 / 1.11.4 / 1.12.4 or later
Fixed in 1.10.41.11.41.12.4
Interim mitigation

Update KNIME Business Hub to version 1.13.3, 1.12.4, 1.11.4, or 1.10.4 or above to patch the ingress-nginx component vulnerability. Alternatively, apply publicly documented workarounds for CVE-2025-1974.

Recommended fix High confidence

1.13.3 (or 1.12.4/1.11.4/1.10.4 depending on current version line)

  1. Determine the currently installed KNIME Business Hub version
  2. Plan the upgrade path based on current version: if 1.10.x upgrade to 1.10.4+, if 1.11.x upgrade to 1.11.4+, if 1.12.x upgrade to 1.12.4+, if 1.13.x upgrade to 1.13.3+
  3. Review KNIME Business Hub upgrade documentation for your deployment method (helm, operator, or manual)
  4. Backup the current Business Hub configuration and any persistent data
  5. Perform the upgrade using the appropriate deployment method
  6. Verify the ingress-nginx component has been updated to the fixed version
  7. Confirm KNIME Business Hub is running correctly after upgrade

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

Fix this in Business Hub Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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