CVE-2026-86080: CWE-347: Improper Verification of Cryptographic Signature in n8n-io n8n
Description
CVE-2026-86080 is a medium severity vulnerability in the n8n open source workflow automation platform. It involves improper verification of cryptographic signatures in the GitHub Trigger node. Prior to fixed versions, the webhook secret was discarded under certain error conditions, causing the system to accept webhook deliveries without proper signature verification. This issue is resolved in n8n versions 1.123.76, 2.37.7, and 2.38.2.
CVSS v4.0
Score 6.3medium
Affected software
n8n-io
n8n
pkg:github/n8n-io/n8nRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in n8n's GitHub Trigger node arises when the webhook secret generated during webhook creation is discarded if GitHub returns an HTTP 422 error and the node reuses an existing webhook. This leads to workflow static data retaining a webhookId without the corresponding webhookSecret. Consequently, the X-Hub-Signature-256 verification process accepts webhook deliveries without a stored secret, effectively bypassing signature verification. The affected code includes the file packages/nodes-base/nodes/Github/GithubTriggerHelpers.ts and the logic path handling the 422 webhook reuse. The issue is fixed in versions 1.123.76, 2.37.7, and 2.38.2.
Potential Impact
An attacker could potentially send webhook deliveries that bypass signature verification, which may allow unauthorized or spoofed webhook events to be accepted by the n8n platform. This could lead to unauthorized workflow executions or other unintended actions triggered by malicious webhook payloads. The CVSS 4.0 base score is 6.3, indicating a medium severity impact with network attack vector, low attack complexity, no privileges required, no user interaction, and limited impact on integrity.
Mitigation Recommendations
This vulnerability is fixed in n8n versions 1.123.76, 2.37.7, and 2.38.2. Users should upgrade to these or later versions to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-09-04T19:34:03.100Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6aa08023acd9273b4940c39e
Added to database: 09/08/2026, 21:37:39 UTC
Last enriched: 09/16/2026, 02:43:56 UTC
Last updated: 10/08/2026, 18:48:49 UTC
Views: 79
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.