CVE-2026-21894: N8n N8n's Missing Stripe-Signature Verification Allows Vulnerability
MODERATECVE-2026-21894 is a MODERATE (CVSS 6.5) n8n's missing stripe-signature verification allows vulnerability (CWE-290: Authentication Bypass by Spoofing) affecting N8n libraries in the npm ecosystem. The issue involves n8n's missing stripe-signature verification allows unauthenticated forged webhooks. Remediation is available by upgrading affected packages to version 2.2.2.
CVE-2026-21894 at a Glance
Security Impact
CVSS: 6.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N).
How to Fix CVE-2026-21894
To remediate this vulnerability, upgrade all affected N8n dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install n8n@2.2.2
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls n8n
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-21894, inspect your project dependencies using npm:
npm ls n8n
Analyze the terminal output to locate any version of N8n in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.2.2), your application is affected.
Note: The npm ls n8n command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-290: Authentication Bypass by Spoofing, where this attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks. In N8n, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-21894 Affected N8n Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
n8n
|
npm |
≥ 0.150.0
< 2.2.2
|
2.2.2
|
References
Frequently Asked Questions
What is CVE-2026-21894?
Which N8n versions are affected?
What version fixes CVE-2026-21894?
Is n8n affected?
What is the CVSS score of CVE-2026-21894?
What CWE is associated with CVE-2026-21894?
How can I check npm dependencies for CVE-2026-21894?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-jf52-3f2h-h9j5",
"modified" : "2026-01-08T20:51:27Z",
"published" : "2026-01-07T19:22:54Z",
"aliases" : [ "CVE-2026-21894" ],
"summary" : "n8n's Missing Stripe-Signature Verification Allows Unauthenticated Forged Webhooks",
"details" : "### Impact\nAn authentication bypass in the Stripe Trigger node allows unauthenticated parties to trigger workflows by sending forged Stripe webhook events.\n\nThe Stripe Trigger creates and stores a Stripe webhook signing secret when registering the webhook endpoint, but incoming webhook requests were not verified against this secret. As a result, any HTTP client that knows the webhook URL could send a POST request containing a matching event `type`, causing the workflow to execute as if a legitimate Stripe event had been received.\n\nThis issue affects n8n users who have active workflows using the Stripe Trigger node. An attacker could potentially fake payment or subscription events and influence downstream workflow behavior. The practical risk is reduced by the fact that the webhook URL contains a high-entropy UUID; however, authenticated n8n users with access to the workflow can view this webhook ID.\n\n### Patches\nThe issue has been fixed in n8n version 2.2.2. Users should upgrade to this version or later to ensure that Stripe webhook signatures are properly verified.\n\n### Workarounds\nThere is no complete workaround short of upgrading. As a temporary mitigation, users can deactivate affected workflows or restrict access to workflows containing Stripe Trigger nodes to trusted users only.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "n8n"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0.150.0"
}, {
"fixed" : "2.2.2"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/n8n-io/n8n/security/advisories/GHSA-jf52-3f2h-h9j5"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-21894"
}, {
"type" : "WEB",
"url" : "https://github.com/n8n-io/n8n/pull/22764"
}, {
"type" : "WEB",
"url" : "https://github.com/n8n-io/n8n/commit/a61a5991093c41863506888336e808ac1eff8d59"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/n8n-io/n8n"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-290" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-01-07T19:22:54Z",
"nvd_published_at" : "2026-01-08T10:15:55Z"
}
}