CVE-2026-86080Network attack vector

Unauthenticated workflow execution via missing webhook secret

Published Sep 8, 2026 · Updated Sep 9, 2026

Improper signature verification in the n8n GitHub Trigger allows remote attackers to submit forged webhook deliveries that trigger workflows. In GithubTriggerHelpers.ts, the HTTP 422 webhook-reuse path stores webhookId without the generated webhookSecret, and verification accepts X-Hub-Signature-256 deliveries when that secret is absent. Exploitation requires an existing webhook to cause the 422 reuse state and knowledge of its callback URL; accepted deliveries can invoke the workflow's configured actions.

CVSS severity6.3
Medium
EPSS probability0.16%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper signature verification in the n8n GitHub Trigger allows remote attackers to submit forged webhook deliveries that trigger workflows. In GithubTriggerHelpers.ts, the HTTP 422 webhook-reuse path stores webhookId without the generated webhookSecret, and verification accepts X-Hub-Signature-256 deliveries when that secret is absent. Exploitation requires an existing webhook to cause the 422 reuse state and knowledge of its callback URL; accepted deliveries can invoke the workflow's configured actions.

The record

CVE
CVE-2026-86080
Published
Sep 8, 2026
Updated
Sep 9, 2026
Vendor
n8n
Product
n8n
Classifications
CWE-347, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Sep 8, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 9, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 1.123.76
  2. Affected versionversion=>= 2.0.0, < 2.37.7
  3. Affected versionversion=>= 2.38.0, < 2.38.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

n8n · n8nversion=< 1.123.76; version=>= 2.0.0, < 2.37.7; version=>= 2.38.0, < 2.38.2

Published CVSS scores

6.3GitHub CNACVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-347Improper Verification of Cryptographic Signature
T1190Exploit Public-Facing Application

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo