Skip to main content
VulnerabilityPublished

CVE-2026-54308: n8n · Authentication Bypass by Spoofing

Affects n8nSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.26.2 or 2.25.7 when convenient.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.26.2, 2.25.7
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade n8n and n8n-io/n8n to 2.26.2 or 2.25.7.

Affected software

ProductAffectedFixed in
n8n-ion8nAffected
  • >=2.26.0 <2.26.2
Fixed in
  • 2.26.2
n8n-ion8nAffected
  • <2.25.7
Fixed in
  • 2.25.7
GitHubn8n-io/n8npkg:github/n8n-io/n8nOther threatsAffected
  • <2.25.7
  • >=2.25.0 <2.25.7
  • <2.26.2
Fixed in
  • 2.25.7
  • 2.26.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade affected n8n installations to version 2.25.7 or later, or 2.26.2 or later, where the vulnerability is fixed. No other mitigation or temporary workaround is indicated. Patch status is confirmed fixed in these versions.

Description

n8n is an open source workflow automation platform. Prior to 2.25.7 and 2.26.2, the MicrosoftAgent365Trigger and StripeTrigger node did not validate that inbound requests. As a result, an unauthenticated attacker who knows the webhook URL could submit a forged payload and cause the workflow to execute with attacker-controlled data. This vulnerability is fixed in 2.25.7 and 2.26.2.

References

Community reviews

Loading reviews…