Missing Webhook Signature Verification in Webflow Trigger Node Allows Forged Event Injection
GHSA-hwv9-jhc7-f7c4 · published 2026-09-16 · updated 2026-09-17
- Severity
- Medium
- CVSS score
- 6.9
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 2.40.1
The Webflow Trigger node accepted any HTTP POST to its webhook URL without verifying the x-webflow-signature HMAC that Webflow attaches to webhook deliveries. An unauthenticated attacker who knows the webhook URL could send a forged request that impersonates a legitimate Webflow event and triggers the workflow with fully attacker-controlled input. Any downstream nodes that act on the event data — creating or updating records, sending messages, or calling internal APIs — would then operate on that forged payload. The patch adds HMAC signature verification to the webhook handler and rejects requests that do not carry a valid signature. …
Upgrade n8n to 2.40.1 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
The issue has been fixed in n8n versions 1.123.80, 2.39.6 and 2.40.1. Users should upgrade to one of these versions or later to remediate the vulnerability.
If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Deactivate any workflows using the Webflow Trigger node if they are not currently required. Restrict network-level access to the n8n webhook endpoint to Webflow's published IP ranges only. Restrict n8n instance access to fully trusted users only. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- CriticalFlowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromiumflowise, flowise-components
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- Criticaln8n Has an Arbitrary File Read via Git Noden8n, n8n, n8n
- Criticaln8n: HTTP Request Node Pagination Prototype Pollution to RCEn8n, n8n, n8n
- Criticaln8n Has an XML Node Prototype Pollution Patch Bypassn8n, n8n, n8n
- Criticaln8n has XML Node Prototype Pollution that to RCEn8n, n8n, n8n
- Criticaln8n has Prototype Pollution in XML Webhook Body Parser that Leads to RCEn8n, n8n, n8n
The impact, patch and workaround text comes from the advisory, shortened (published by n8n). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.