Summary
Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Deactivate any workflows using the Microsoft Agent 365 Trigger node or Stripe Trigger node until the instance can be upgraded.
- Restrict network access to the n8n webhook endpoint to trusted sources only.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Impact
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.
CVE-2026-54308 has a CVSS score of 7.2 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.26.2, 2.25.7); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
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.
Frequently Asked Questions
- What is CVE-2026-54308? CVE-2026-54308 is a medium-severity security vulnerability in n8n (npm), affecting versions >= 2.26.0, < 2.26.2. It is fixed in 2.26.2, 2.25.7.
- How severe is CVE-2026-54308? CVE-2026-54308 has a CVSS score of 7.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of n8n are affected by CVE-2026-54308? n8n (npm) versions >= 2.26.0, < 2.26.2 is affected.
- Is there a fix for CVE-2026-54308? Yes. CVE-2026-54308 is fixed in 2.26.2, 2.25.7. Upgrade to this version or later.
- Is CVE-2026-54308 exploitable, and should I be worried? Whether CVE-2026-54308 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-54308 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-54308?
- Upgrade
n8nto 2.26.2 or later - Upgrade
n8nto 2.25.7 or later
- Upgrade