dbcve.org
N8nApplication

CVE-2026-56357

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-22
Fix available
A fix is available. Upgrade to 1.123.15 / 2.5.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
n8n before 1.123.15 and 2.5.0 contains a webhook forgery vulnerability in the GitHub Webhook Trigger node that fails to implement HMAC-SHA256 signature verification. Attackers who know the webhook URL can send unsigned POST requests to trigger workflows with arbitrary data, spoofing GitHub webhook events.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The GitHub Webhook Trigger node in n8n versions prior to 1.123.15 and 2.5.0 fails to implement HMAC-SHA256 signature verification on incoming webhook requests. An attacker who discovers the webhook URL can send unsigned POST requests containing arbitrary data that will trigger configured workflows, effectively spoofing legitimate GitHub webhook events.

MitigationUpgrade n8n to version 1.123.15 or 2.5.0 or later which implements proper HMAC-SHA256 signature verification for the GitHub Webhook Trigger node.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
N8nApplication
Affected:< 1.123.15>= 2.0.0, < 2.5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify n8n installation version
    Run `n8n --version` from the command line, or check the version displayed in the n8n UI footer at the bottom of the page. Alternatively, inspect the package.json file in the n8n installation directory for the version field.
    Affected if The installed version is below 1.123.15 for the 1.x branch, OR between 2.0.0 and 2.5.0 (exclusive of 2.5.0) for the 2.x branch.
  2. Locate GitHub Webhook Trigger nodes in workflows
    Open the n8n UI, navigate to the Workflows section, and search for workflows that include a GitHub Webhook Trigger node. Check each workflow that uses this node type.
    Affected if Any workflow uses the GitHub Webhook Trigger node in an affected n8n version.
  3. Verify HMAC-SHA256 signature verification configuration
    Open any workflow containing a GitHub Webhook Trigger node, then open the node settings panel. Look for a field labeled 'Verification' or 'Signature Verification' with an option to enable HMAC-SHA256 verification.
    Affected if The HMAC-SHA256 signature verification option is missing, disabled, or not present in the node configuration settings.
  4. Inspect webhook URL accessibility
    Review the GitHub Webhook Trigger node in each workflow to identify the webhook URL. Determine if this URL is exposed or discoverable outside the organization.
    Affected if The webhook URL is publicly accessible and the n8n version is vulnerable, meaning unsigned requests can trigger the workflow.

You are affected if your n8n version falls within the vulnerable ranges AND you have workflows using the GitHub Webhook Trigger node, as the missing HMAC-SHA256 signature verification allows attackers to spoof GitHub events.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.123.15 / 2.5.0 or later
Fixed in 1.123.152.5.0
Interim mitigation

Upgrade n8n to version 1.123.15 or 2.5.0 or later which implements proper HMAC-SHA256 signature verification for the GitHub Webhook Trigger node.

Recommended fix High confidence

n8n 1.123.15 (for 1.x line) or n8n 2.5.0+ (for 2.x line)

  1. Identify which n8n major version line you are currently running (1.x or 2.x)
  2. If running version 1.x: Upgrade to n8n version 1.123.15 or later
  3. If running version 2.x: Upgrade to n8n version 2.5.0 or later
  4. After upgrading, verify that your GitHub Webhook Trigger workflows still function correctly
  5. Ensure your GitHub webhook URL remains secure and not exposed publicly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in N8n Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56357 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-56357 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data