CVE-2026-54308Medium· 7.2▾ Sunlitn8n: Missing Token Validation on Microsoft Agent 365 Trigger and Stripe Nodes
▾ Sunlit zone — Low / medium · no exploitation signal
impact 39.6 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 4.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via GHSA
0.3%
0.3% → 0.3%
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.
The issue has been fixed in n8n versions 2.25.7, and 2.26.2. Users should upgrade to one of these versions or later to remediate the vulnerability.
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
n8n >= 2.26.0, < 2.26.2n8n < 2.25.7Upgrade to a patched release:
n8n 2.26.2n8n 2.25.7Connected by shared product, vendor, weakness, or advisory.
CVE-2026-86083High· 8.8n8n is an open source workflow automation platform
CVE-2026-86084Medium· 5.5n8n is an open source workflow automation platform
CVE-2026-86085Medium· 4.9n8n is an open source workflow automation platform
CVE-2026-86994Medium· 4.3n8n is an open source workflow automation platform
CVE-2026-86075High· 7.5n8n is an open source workflow automation platform
CVE-2026-86076High· 8.8n8n is an open source workflow automation platform