CVE-2026-56357: n8n before 1.123.15 and 2.5.0 contains a webhook forgery vulnerability in the GitHub Webhook Trigger node that

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

n8n: upgrade to 1.123.15, 2.5.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-56357 being exploited?

CVE-2026-56357 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-56357 affect?

CVE-2026-56357 affects n8n. Severity is medium (CVSS 4.0). 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 trig

Q: How urgent is CVE-2026-56357?

Priority 25/100. Remotely exploitable, no login, no user action

Routine

MEDIUM 4.0REMOTEUPGRADE

CVE-2026-56357 is a medium-severity flaw (CVSS 4.0) affecting n8n. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	4.0 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 76%)
CISA exploited list	No
Weakness	CWE-290
Published	2026-06-22
Last modified	2026-06-24

Publisher (CNA): VulnCheck · Vendor: n8n

Last updated 2026-06-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-22 22:16 UTCPublished CVE record published
2026-06-24 16:47 UTCUpdated Record last modified

n8n n8n UPGRADE

Affected: < 1.123.15 · >= 2.0.0 and < 2.5.0

Fixed in: 1.123.15, 2.5.0

Safe to downgrade to: a release before 2.0.0

1. Check installed version

npm ls n8n

2. UPGRADE to 1.123.15

npm install n8n@">=1.123.15"

3. If no update is available yet, DOWNGRADE to a release before 2.0.0

npm view n8n versions npm install n8n@"<2.0.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-56357?

n8n: upgrade to 1.123.15, 2.5.0. Exact commands for each OS are on this page.

Is CVE-2026-56357 being exploited?

CVE-2026-56357 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-56357 affect?

CVE-2026-56357 affects n8n. Severity is medium (CVSS 4.0). 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 trig

How urgent is CVE-2026-56357?

Priority 25/100. Remotely exploitable, no login, no user action

Software pages

GitHub vulnerabilities

Related CVEs

CVE-2026-54309 CRITICAL 10.0 UPGRADE n8n is an open source workflow automation platform
CVE-2026-54310 CRITICAL 9.9 UPGRADE n8n is an open source workflow automation platform
CVE-2026-44789 CRITICAL 9.9 UPGRADE n8n is an open source workflow automation platform
CVE-2026-44791 CRITICAL 9.9 UPGRADE n8n is an open source workflow automation platform
CVE-2026-54314 HIGH 7.5 UPGRADE n8n is an open source workflow automation platform

References

← Back to latest CVEs