# CVE-2026-115494: CSRF protection could be tricked by forged X-Forwarded-Host header in KNIME Business Hub


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/U:Green`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-4rqh-69w9-947v

## What is CVE-2026-115494?

CVE-2026-115494 is a medium-severity vulnerability in KNIME Business Hub, published on 22 Oct 2026. 

### Official description

A flaw in the cross-site request forgery (CSRF) prevention of KNIME Business Hub prior to version 1.19.0 allows an authenticated attacker to perform a CSRF attack with passive user interaction. This means the state of a resource could be changed without the user noticing. As a workaround, an API gateway for firewall in front of KNIME Business Hub could remove the X-Forwaded-For header from all incoming requests.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-115494?


## How do I fix CVE-2026-115494?

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

## Is CVE-2026-115494 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115494 and fix it if it is affected.

What it is: CVE-2026-115494 is a medium-severity vulnerability in KNIME Business Hub, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115494 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-2026-115494/ (Markdown: https://insights.sbomify.com/CVE-2026-115494/index.md)
```

## Sources

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

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