CVE-2026-115494 KNIME CVE debrief

Who should care

Defenders responsible for KNIME Business Hub deployments should assess exposure and apply the vendor-provided fix or workaround to prevent potential CSRF attacks. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify exposure and implement necessary mitigations.

Why it matters

A CSRF prevention flaw in KNIME Business Hub allows authenticated attackers to perform CSRF attacks with passive user interaction, potentially changing the state of a resource without the user's knowledge. Defenders should prioritize verifying exposure and applying the vendor-provided fix or workaround.

• An attacker could change the state of a resource without the user's knowledge
• Defenders need to verify exposure and apply the vendor-provided fix or workaround
• Passive user interaction is required for the attack

Technical summary

The CSRF prevention mechanism in KNIME Business Hub prior to version 1.19.0 can be tricked by a forged X-Forwarded-Host header, allowing an authenticated attacker to perform a CSRF attack with passive user interaction. This vulnerability is addressed in version 1.19.0. Defenders should prioritize verifying exposure and applying the vendor-provided fix or workaround, especially for systems with untrusted or unauthenticated access. The attack requires passive user interaction and can change the state of a resource without the user's knowledge.

Defensive priority

Defenders should prioritize verifying exposure and applying the vendor-provided fix or workaround, especially for systems with untrusted or unauthenticated access.

Recommended defensive actions

• Verify if KNIME Business Hub is deployed and assess the version
• Apply the vendor-provided fix (version 1.19.0) or recommended workaround
• Monitor for suspicious activity related to CSRF attacks
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the CSRF prevention flaw in KNIME Business Hub. The vendor has provided a fixed version (1.19.0) and a workaround involving an API gateway. Evidence is limited to CVE Program and NVD details. Defenders should verify exposure and apply the fix or workaround, monitoring for suspicious CSRF-related activity.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.