Skip to main content
VulnerabilityPublished

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

Affects n8nSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.2.2 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.2.2
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade n8n and n8n-io/n8n to 2.2.2.

Affected software

ProductAffectedFixed in
n8n-ion8nAffected
  • >=0.150.0 <2.2.2
Fixed in
  • 2.2.2
npmn8n-io/n8npkg:npm/n8n-io/n8nOther threatsAffected
  • >=0.150.0 <2.2.2
Fixed in
  • 2.2.2

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

AI-suggested

  1. Upgrade n8n installations to version 2.2.2 or later, which includes the patch verifying Stripe webhook requests against the stored signing secret.
  2. Until patching is possible, deactivate all workflows that use the Stripe Trigger node to prevent unauthorized triggering.
  3. Restrict access to workflows containing Stripe Trigger nodes strictly to trusted and authorized users to minimize the risk of webhook URL exposure.
  4. Implement network-level controls such as IP whitelisting or firewall rules to limit incoming requests to the webhook URL from known Stripe IP ranges.
  5. Monitor workflow execution logs for unusual or unexpected Stripe event triggers that could indicate exploitation attempts.
  6. Educate users with access to n8n workflows about the sensitivity of webhook URLs and enforce strict credential management policies.
  7. Consider adding additional verification layers in workflows to validate event authenticity, such as checking event payload signatures manually if feasible.
  8. Regularly audit n8n configurations and access controls to ensure compliance with security best practices.

Description

CVE-2026-21894 is an authentication bypass vulnerability in the n8n workflow automation platform affecting versions 0.150.0 to before 2.2.2. The flaw exists in the Stripe Trigger node, where incoming webhook requests are not verified against the stored Stripe webhook signing secret. This allows unauthenticated attackers who know the webhook URL to send forged Stripe webhook events, triggering workflows without legitimate Stripe events. The risk is somewhat mitigated by the high-entropy UUID in the webhook URL, but authenticated users can view this URL, increasing exposure. Exploitation could lead to fake payment or subscription events influencing downstream processes. The vulnerability has been patched in version 2.

References

Community reviews

Loading reviews…