What is CVE-2026-86080?

CVE-2026-86080 is a medium-severity security vulnerability in n8n (npm), affecting versions < 1.123.76. It is fixed in 1.123.76, 2.38.2, 2.37.7.

Which versions of n8n are affected by CVE-2026-86080?

n8n (npm) versions < 1.123.76 is affected.

Is there a fix for CVE-2026-86080?

Yes. CVE-2026-86080 is fixed in 1.123.76, 2.38.2, 2.37.7. Upgrade to this version or later.

Is CVE-2026-86080 exploitable, and should I be worried?

Whether CVE-2026-86080 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-86080 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-86080?

Upgrade: n8n to 1.123.76 or later, n8n to 2.38.2 or later, n8n to 2.37.7 or later.

CVE-2026-86080 in n8n

Q: Which versions of n8n are affected by CVE-2026-86080?

n8n (npm) versions < 1.123.76 is affected.

Q: Is there a fix for CVE-2026-86080?

Yes. CVE-2026-86080 is fixed in 1.123.76, 2.38.2, 2.37.7. Upgrade to this version or later.

Q: Is CVE-2026-86080 exploitable, and should I be worried?

Whether CVE-2026-86080 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-86080 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-86080?

Upgrade: n8n to 1.123.76 or later, n8n to 2.38.2 or later, n8n to 2.37.7 or later.

Summary

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

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.

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.

Affected versions

n8n (< 1.123.76) n8n (>= 2.38.0, < 2.38.2) n8n (>= 2.0.0, < 2.37.7)

Security releases

n8n → 1.123.76 (npm) n8n → 2.38.2 (npm) n8n → 2.37.7 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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.

Frequently Asked Questions

What is CVE-2026-86080? CVE-2026-86080 is a medium-severity security vulnerability in n8n (npm), affecting versions < 1.123.76. It is fixed in 1.123.76, 2.38.2, 2.37.7.
Which versions of n8n are affected by CVE-2026-86080? n8n (npm) versions < 1.123.76 is affected.
Is there a fix for CVE-2026-86080? Yes. CVE-2026-86080 is fixed in 1.123.76, 2.38.2, 2.37.7. Upgrade to this version or later.
Is CVE-2026-86080 exploitable, and should I be worried? Whether CVE-2026-86080 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-86080 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-86080?
- Upgrade n8n to 1.123.76 or later
- Upgrade n8n to 2.38.2 or later
- Upgrade n8n to 2.37.7 or later