Quick answers
- Is CVE-2026-115494 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115494 being exploited in the wild.
- How severe is CVE-2026-115494?
- Informational severity, published 22 October 2026.
- Which products and versions are affected?
- Knime Business Hub prior to 1.19.0.
- Is there a fix for CVE-2026-115494?
- Yes: fixed in KNIME Business Hub 1.19.0. Until then: Deploy an API gateway or firewall in front of KNIME Business Hub to remove the X-Forwarded-For header from all incoming requests. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-115494 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-115494?
- Check whether you run Knime Business Hub at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: KNIME Business Hub 1.19.0
Deploy an API gateway or firewall in front of KNIME Business Hub to remove the X-Forwarded-For header from all incoming requests.
Technical details
The CSRF prevention mechanism in KNIME Business Hub prior to 1.19.0 can be bypassed by forging the X-Forwarded-Host header, allowing an attacker to perform unauthorized actions. The vulnerability requires authentication and user interaction (passive, such as visiting a malicious page while logged in). An attacker can modify resource state without explicit user consent.
Affected products
- KNIME Business Hub prior to 1.19.0
Timeline
- 2026-10-22: disclosed