CVE-2026-86080: n8n GitHub Trigger 422 Reuse Path Vulnerability

MODERATE
Advisory Identifier: GHSA-5m98-cgcr-xx3q
Share
CWE-347
Published
Advisory Summary

CVE-2026-86080 is a MODERATE github trigger 422 reuse path vulnerability (CWE-347: Improper Verification of Cryptographic Signature) affecting n8n libraries in the npm ecosystem. The issue involves github trigger 422 reuse path skips webhook secret storage, causing signature verification to fail-open. Remediation is available by upgrading affected packages to version 1.123.76, 2.38.2, 2.37.7.

CVE-2026-86080 at a Glance

CVE Identifier CVE-2026-86080
GHSA Identifier GHSA-5m98-cgcr-xx3q
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-347: Improper Verification of Cryptographic Signature
Affected Product n8n
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-86080

To remediate this vulnerability, upgrade all affected n8n dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

n8n fixed: 1.123.76 
npm install n8n@1.123.76
n8n fixed: 2.38.2 
npm install n8n@2.38.2
n8n fixed: 2.37.7 
npm install n8n@2.37.7
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls n8n

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-86080, inspect your project dependencies using npm:

npm ls n8n

Analyze the terminal output to locate any version of n8n in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.123.76), your application is affected.

Note: The npm ls n8n command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-347: Improper Verification of Cryptographic Signature, where the product does not verify, or incorrectly verifies, the cryptographic signature for data. In n8n, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Impact 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. ## Patches The issue has been fixed in n8n versions 1.123.76, 2.37.7, and 2.38.2. Users should upgrade to one of these versions or later to remediate the vulnerability. ## 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. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

CVE-2026-86080 Affected n8n Versions

3 component(s)
Fixed Versions:
1.123.762.38.22.37.7
Product / Package Ecosystem Affected Versions Fixed Version
n8n
npm/n8n
npm
< 1.123.76
1.123.76
n8n
npm/n8n
npm
≥ 2.38.0
< 2.38.2
2.38.2
n8n
npm/n8n
npm
≥ 2.0.0
< 2.37.7
2.37.7

References

GitHub Advisory / Wiki ADVISORY
https://github.com/n8n-io/n8n/security/advisories/GHSA-5m98-cgcr-xx3q
NVD — CVE-2026-86080 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-86080
n8n Source Repository REPOSITORY
https://github.com/n8n-io/n8n
n8n Release RELEASE
https://github.com/n8n-io/n8n/releases/tag/n8n@1.123.76
n8n Release RELEASE
https://github.com/n8n-io/n8n/releases/tag/n8n@2.37.7
n8n Release RELEASE
https://github.com/n8n-io/n8n/releases/tag/n8n@2.38.2

Frequently Asked Questions

What is CVE-2026-86080?
CVE-2026-86080 is a security vulnerability in n8n involving GitHub Trigger 422 Reuse Path Skips Webhook Secret Storage, Causing Signature Verification to Fail-Open under CWE-347: Improper Verification of Cryptographic Signature.
Which n8n versions are affected?
Affected versions include releases prior to 1.123.76, 2.38.2, 2.37.7 across affected packages: n8n.
What version fixes CVE-2026-86080?
Upgrading to 1.123.76, 2.38.2, 2.37.7 (or the latest patched release for your respective branch) resolves the vulnerability.
Is n8n affected?
Yes, n8n is affected in releases prior to 1.123.76, 2.38.2, 2.37.7. Upgrade your dependency to 1.123.76, 2.38.2, 2.37.7 or later.
What CWE is associated with CVE-2026-86080?
CVE-2026-86080 is classified under CWE-347: Improper Verification of Cryptographic Signature (The product does not verify, or incorrectly verifies, the cryptographic signature for data.).
How can I check npm dependencies for CVE-2026-86080?
Run the dependency tree command: 'npm ls n8n'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5m98-cgcr-xx3q",
  "modified" : "2026-09-10T21:06:37Z",
  "published" : "2026-09-10T21:06:37Z",
  "aliases" : [ "CVE-2026-86080" ],
  "summary" : "n8n: GitHub Trigger 422 Reuse Path Skips Webhook Secret Storage, Causing Signature Verification to Fail-Open",
  "details" : "## Impact\n\nThe 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.\n\n## Patches\n\nThe issue has been fixed in n8n versions 1.123.76, 2.37.7, and 2.38.2. Users should upgrade to one of these versions or later to remediate the vulnerability.\n\n## Workarounds\n\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- 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.\n- Restrict network access to the n8n webhook endpoint to GitHub's published IP ranges only.\n- Audit GitHub Trigger workflow static data for entries that contain a `webhookId` but no `webhookSecret`, and treat those workflows as unprotected until reactivated successfully.\n\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.123.76"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.38.0"
      }, {
        "fixed" : "2.38.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0"
      }, {
        "fixed" : "2.37.7"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/security/advisories/GHSA-5m98-cgcr-xx3q"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-86080"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/n8n-io/n8n"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@1.123.76"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@2.37.7"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@2.38.2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-347" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-10T21:06:37Z",
    "nvd_published_at" : "2026-09-08T22:19:16Z"
  }
}