CVE-2026-54308 Details
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.
A vulnerability exists in n8n workflow automation platform versions prior to 2.25.7 and 2.26.2, where the MicrosoftAgent365Trigger and StripeTrigger nodes failed to validate incoming requests. This lack of validation allowed an unauthenticated attacker, aware of the webhook URL, to send a forged payload that would be executed within the workflow, using data controlled by the attacker.
Users are advised to upgrade to n8n versions 2.25.7 or 2.26.2. If an immediate upgrade is not possible, deactivate workflows using the Microsoft Agent 365 Trigger or Stripe Trigger nodes, and restrict network access to the n8n webhook endpoint to trusted sources only.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jun 24, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/n8n-io/n8n/security/advisories/GHSA-jvc7-762p-3743 | [email protected] | MitigationVendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-290 | Authentication Bypass by Spoofing | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| n8n n8n | < 2.25.7 >= 2.26.0, < 2.26.2 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 26, 2026 | Initial Analysis | [email protected] |
| Jun 24, 2026 | CVE Modified | CISA-ADP |
| Jun 23, 2026 | New CVE Received | [email protected] |