Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-21894: n8n's Missing Stripe-Signature Verification Allows Unauthenticated Forged Webhooks

MediumCVSS 6.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 26/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.47% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: n8n-io n8n 2.2.2.

Low priority for now. Upgrade to n8n-io n8n 2.2.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

n8n is an open source workflow automation platform. In versions from 0.150.0 to before 2.2.2, an authentication bypass vulnerability in the Stripe Trigger node allows unauthenticated parties to trigger workflows by sending forged Stripe webhook events. The 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. This 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. This issue has been patched in version 2.2.2. A temporary workaround for this issue involves users deactivating affected workflows or restricting access to workflows containing Stripe Trigger nodes to trusted users only.

Published
Jan 8, 2026
Updated
Jun 17, 2026
EPSS
0.4% · 41th percentile

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
6.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-21894

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
n8nn8n

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • n8n-io n8n

    • >= 0.150.0, < 2.2.2affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • n8n n8n0.150.0 and later · before 2.2.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
npmn8nfrom 0.150.0 · before 2.2.22.2.2

Same product

n8n: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-68613n8n Vulnerable to Remote Code Execution via Expression InjectionKEV
    95Now
  • CVE-2026-21858n8n Vulnerable to Unauthenticated File Access via Improper Webhook Request Handling
    63This week
  • CVE-2026-1470Authenticated users can bypass the Expression sandbox mechanism to achieve full remote code execution on n8n’s main node.
    45Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-68697Dec 26, 2025 · Self-hosted n8n has Legacy Code node that enables arbitrary file read/write
    21Monitor
  • ← EarlierCVE-2026-21877Jan 7, 2026 · n8n is vulnerable to Remote Code Execution via Arbitrary File Write
    41Plan
  • Later →CVE-2025-68949Jan 13, 2026 · n8n has a Webhook Node IP Whitelist Bypass via Partial String Matching
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
n8n-io n8n2.2.2 · descriptionVendor (CNA)
npm:n8n2.2.2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-56357165 days apartn8n - Webhook Forgery via Missing HMAC-SHA256 Signature Verification in GitHub Webhook Trigger
    25Monitor
  • CVE-2026-54308166 days apartn8n: Missing Token Validation on Microsoft Agent 365 Trigger Node
    25Monitor
  • CVE-2026-56360181 days apartn8n - Webhook Forgery via Unsigned POST Requests in ZendeskTrigger
    25Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

  • CVE-2025-6866813 days apartn8n Vulnerable to Arbitrary Command Execution in Pyodide based Python Code Node
    43Plan
  • CVE-2026-086310 days apartSandbox escape in n8n Python task runner allows for arbitrary code execution on the underlying host.
    42Plan
  • CVE-2026-218771 days apartn8n is vulnerable to Remote Code Execution via Arbitrary File Write
    41Plan
  • CVE-2025-6191413 days apartn8n's Possible Stored XSS in "Respond to Webhook" Node May Execute Outside iframe Sandbox
    21Monitor

Not on record for this CVE: EPSS history · researcher credit · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
low · data can be read
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
High
Availability impact
None

CVSS vector

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

nvd-secondary

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records