All vulnerabilities

Servers and applications

CVE-2026-86080

GitHub Trigger 422 Reuse Path Skips Webhook Secret Storage, Causing Signature Verification to Fail-Open

Severity
Medium 6.3
Published
2 Sept 2026
Last changed
11 Sept 2026
Added to UpHeron
1 Nov 2026
Fixed in
1.123.76, 2.37.7, 2.38.2
Exploit chance
0.3% in the next 30 daysHigher than 17% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Improper verification of a cryptographic signature (CWE-347)
Attack
Over the network · Only under certain conditions · No login needed · No user action needed
Attacker can
Change some data
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Also known as
GHSA-5m98-cgcr-xx3q
Sources
NVD, Project advisories (GitHub)

Description

The GitHub Trigger generated a signing secret when it registered a webhook and verified X-Hub-Signature-256 on each delivery. When GitHub answered the create request with a 422 because a webhook for the URL already existed, the node adopted the remote hook but kept only its id and events, discarding the secret it had generated. Deliveries to that workflow's webhook URL were then accepted from anyone. The patch re-fetches the existing hook by its stored id, re-applies the signing secret, and makes verification fail closed when no secret is stored.

From n8n-io/n8n's security advisory.

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

  • Deactivate and reactivate any GitHub Trigger workflows to force a fresh webhook registration with a new secret, provided the remote GitHub hook has been deleted first so that the 422 reuse path is not taken again.
  • Restrict network access to the n8n webhook endpoint to GitHub's published IP ranges only.
  • Audit GitHub Trigger workflow static data for entries that contain a webhookId but no webhookSecret, and treat those workflows as unprotected until reactivated successfully.
Workarounds as given by n8n-io/n8n's security advisory.

Affected software

SoftwareAffected versions
n8nServers and applications · cpe:a:n8n:n8n
  • Every version before 1.123.76
  • From 2.0.0 before 2.37.7
  • From 2.38.0 before 2.38.2
n8nServers and applications · github:n8n-io/n8n
  • Every version before 1.123.76
  • Every version before 2.38.2
  • Every version before 2.37.7

About n8n

low-code automation tool

From Wikidata, CC0 1.0.
Weekly downloads (npm)
103,525npm, 15 Nov 2026
Docker Hub pulls
286,090,810Docker Hub, 15 Nov 2026
GitHub stars
210,541GitHub, 15 Nov 2026
Forks
61,525GitHub, 15 Nov 2026
Latest release
[email protected]GitHub, 15 Nov 2026
Released
13 Nov 2026GitHub
Written in
TypeScript, Node.jsWikidata
First released
2019Wikidata
First published on GitHub
22 Jun 2019GitHub

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-86080
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-86080
  • GitHub Advisory Database https://github.com/advisories/GHSA-5m98-cgcr-xx3q
  • github.com https://github.com/n8n-io/n8n/security/advisories/GHSA-5m98-cgcr-xx3q