Unauthenticated workflow execution via unsigned Stripe webhooks
Published Jan 8, 2026 · Updated Jan 8, 2026
Authentication bypass in n8n 0.150.0 through 2.2.1 allows remote attackers to execute active workflows via forged Stripe webhooks. The Stripe Trigger webhook handler accepts the event type from the request body without validating the Stripe-Signature HMAC against its signing secret. Exploitation requires an active Stripe Trigger workflow and knowledge of its high-entropy webhook URL; forged payment or subscription events can influence downstream workflow behavior.
Summary
What happened
Authentication bypass in n8n 0.150.0 through 2.2.1 allows remote attackers to execute active workflows via forged Stripe webhooks. The Stripe Trigger webhook handler accepts the event type from the request body without validating the Stripe-Signature HMAC against its signing secret. Exploitation requires an active Stripe Trigger workflow and knowledge of its high-entropy webhook URL; forged payment or subscription events can influence downstream workflow behavior.
The record
- CVE
- CVE-2026-21894
- Published
- Jan 8, 2026
- Updated
- Jan 8, 2026
- Vendor
- n8n
- Product
- n8n
- Classifications
- CWE-290, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 8, 2026CVE publishedPublication date reported by the CVE source.
- Jan 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.150.0, < 2.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo