# CVE-2025-2787: Ingress-nginx vulnerability in KNIME Business Hub

> An attacker with internal cluster access can exploit an ingress-nginx vulnerability to achieve complete Kubernetes cluster takeover.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N/AU:N/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:** 26 Mar 2025
- **Updated:** 8 Apr 2025
- **Also known as:** GHSA-x237-489c-52j2

## What is CVE-2025-2787?

CVE-2025-2787 is a high-severity code injection vulnerability in KNIME Business Hub, published on 26 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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

  *

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2025-2787?

It affects 1 product.


Products: Knime Business Hub.

## How do I fix CVE-2025-2787?

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

## Is CVE-2025-2787 being exploited?

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

## Other vulnerabilities in KNIME Business Hub

- [CVE-2025-2402](https://insights.sbomify.com/CVE-2025-2402/): Hard-coded password for object store of KNIME Business Hub (high 8.8)
- [CVE-2024-6598](https://insights.sbomify.com/CVE-2024-6598/): Denial-of-service on KNIME Business Hub when certain jobs are executed (high 7.1)
- [CVE-2025-14262](https://insights.sbomify.com/CVE-2025-14262/): Jobs can be saved as workflows with wrong permissions on KNIME Business Hub (medium 5.3)
- [CVE-2025-11240](https://insights.sbomify.com/CVE-2025-11240/): Open redirect vulnerability in KNIME Business Hub (medium 5.3)
- [CVE-2025-3019](https://insights.sbomify.com/CVE-2025-3019/): Cross-site scripting vulnerabilities in KNIME Business Hub web pages (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2787 and fix it if it is affected.

What it is: CVE-2025-2787 is a high-severity code injection vulnerability in KNIME Business Hub, published on 26 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2787 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-2025-2787/ (Markdown: https://insights.sbomify.com/CVE-2025-2787/index.md)
```

## Sources

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

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