Webhook Forgery Vulnerability in n8n: Exploiting GitHub Webhook Trigger
Summary
GHSA-mqpr-49jj-32rc: n8n: Webhook Forgery on Github Webhook Trigger. Affects n8n across 2 version ranges.
< 1.123.15
>= 2.0.0, < 2.5.0
Fixed in 1.123.15 or 2.5.0, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
n8n is an open-source workflow automation tool that allows users to connect various applications and services through customizable workflows. It provides a user-friendly interface to create automated tasks without extensive coding knowledge. However, a recent vulnerability has been identified in its GitHub Webhook Trigger node, which could allow unauthorized users to trigger workflows with malicious data.
Vulnerability Detail
The vulnerability arises from the lack of HMAC-SHA256 signature verification in the GitHub Webhook Trigger node of n8n. This oversight allows attackers who know the webhook URL to send unsigned POST requests, effectively spoofing GitHub webhook events. As a result, unauthorized parties can trigger workflows with arbitrary data, potentially leading to data manipulation or unauthorized actions within the n8n environment.
How To Fix
Latest published version: 2.44.6 as of 22 Oct 2026
npm install n8n@2.44.6Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 1.123.151.123.15npm install n8n@1.123.15 -
>= 2.0.0, < 2.5.02.5.0npm install n8n@2.5.0
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
If immediate upgrading is not feasible, consider implementing the following temporary mitigations: 1. Limit workflow creation and editing permissions to fully trusted users only. 2. Restrict network access to the n8n webhook endpoint to known GitHub webhook IP ranges.
Conclusion
The n8n webhook forgery vulnerability poses a significant risk by allowing unauthorized users to trigger workflows. Users are strongly advised to upgrade to the latest versions to mitigate this risk. Temporary workarounds can provide short-term relief but should not replace a proper update.
See every vulnerability recorded for n8n →
FAQ
The vulnerability allows unauthorized users to trigger workflows in n8n by sending unsigned POST requests to the GitHub Webhook Trigger node.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
The risks include unauthorized access to workflows, data manipulation, and the execution of arbitrary actions within the n8n environment.
Yes, upgrading to n8n version 2.5.0 or later, or version 1.123.15 or later will permanently fix the vulnerability.
Implement temporary workarounds such as restricting access to the webhook endpoint and limiting permissions to trusted users.
References
Related vulnerabilities
Recent vulnerabilities recorded for n8n.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
