dbcve.org
Business HubApplication · Knime

CVE-2025-11240

HIGH · 7.2 CVSS v3.1 Published 2025-10-02
Fix available
A fix is available. Upgrade to 1.16.0 or later.
See remediation →
81/100
Remediation priority · High
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
An open redirect vulnerability existed in KNIME Business Hub prior to version 1.16.0. An unauthenticated remote attacker could craft a link to a legitimate KNIME Business Hub installation which, when opened by the user, redirects the user to a page of the attackers choice. This might open the possibility for fishing or other similar attacks. The problem has been fixed in KNIME Business Hub 1.16.0.

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

Open redirect vulnerability in KNIME Business Hub allows unauthenticated attackers to craft malicious URLs that redirect users to attacker-controlled websites. The vulnerability exists in versions prior to 1.16.0 and can be exploited via crafted links to legitimate KNIME Business Hub installations.

MitigationUpgrade KNIME Business Hub to version 1.16.0 or later to remediate this vulnerability. Additionally, implement URL validation and referrer checking at the application or WAF level as a compensating control if immediate upgrade is not feasible.

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.16.0

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 installation version
    Access the KNIME Business Hub administration interface or check the product version through the installed software metadata. Common locations include the web-based admin console, product documentation, or system information pages. Compare the found version against the affected range.
    Affected if The installed version is lower than 1.16.0 (e.g., 1.15.x, 1.14.x, or earlier)
  2. Verify the web interface is accessible
    Confirm that the KNIME Business Hub web interface or API endpoints are exposed and reachable. Open a browser or use a tool like curl to access the base URL of the installation.
    Affected if The web interface is accessible and the version check shows the installation is prior to 1.16.0
  3. Confirm open redirect is exploitable
    Test the redirect functionality by crafting a test URL that includes an external domain parameter (for example, appending a redirect parameter pointing to an external site). Observe whether the application accepts and processes the redirect without proper validation.
    Affected if The application accepts and follows redirects to arbitrary external domains when supplied via URL parameters

If KNIME Business Hub version is below 1.16.0 and its web interface is accessible, the environment is vulnerable to unauthenticated open redirect attacks.

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.16.0 or later
Fixed in 1.16.0
Interim mitigation

Upgrade KNIME Business Hub to version 1.16.0 or later to remediate this vulnerability. Additionally, implement URL validation and referrer checking at the application or WAF level as a compensating control if immediate upgrade is not feasible.

Recommended fix High confidence

KNIME Business Hub 1.16.0

  1. Identify the current KNIME Business Hub version running in your environment
  2. Download KNIME Business Hub version 1.16.0 from the official KNIME website or your authorized distribution channel
  3. Review the official KNIME upgrade documentation for version 1.16.0
  4. Execute the upgrade process according to KNIME's documented procedures
  5. After upgrading, verify that the application is running version 1.16.0
  6. Test that legitimate navigation functions properly and that open redirect behavior is no longer present

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

Fix this in Business Hub Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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