dbcve.org
N8nApplication

CVE-2026-54308

HIGH · 7.2 CVSS v3.1 Published 2026-06-23
Fix available
A fix is available. Upgrade to 2.25.7 / 2.26.2 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The MicrosoftAgent365Trigger and StripeTrigger nodes in n8n fail to validate the authenticity of incoming webhook requests. An unauthenticated attacker who discovers the webhook URL can submit forged payloads, causing workflows to execute with attacker-controlled data instead of legitimate data from Microsoft or Stripe.

MitigationUpgrade to n8n version 2.25.7 or 2.26.2 which implement proper request validation. Until then, restrict webhook URL exposure to trusted networks only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
N8nApplication
Affected:< 2.25.7>= 2.26.0, < 2.26.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check your installed n8n version
    Run 'n8n --version' from command line, or check the version displayed in the n8n UI footer, or query the API endpoint '/rest/version' if exposed
    Affected if The version is less than 2.25.7 OR greater than or equal to 2.26.0 but less than 2.26.2
  2. Identify workflows using MicrosoftAgent365Trigger
    In n8n UI, go to Workflows and search for 'MicrosoftAgent365Trigger', or query the database 'workflows' table for nodes containing 'MicrosoftAgent365Trigger' in the JSON definition
    Affected if Any active or inactive workflow contains a MicrosoftAgent365Trigger node
  3. Identify workflows using StripeTrigger
    In n8n UI, go to Workflows and search for 'StripeTrigger', or query the database 'workflows' table for nodes containing 'StripeTrigger' in the JSON definition
    Affected if Any active or inactive workflow contains a StripeTrigger node
  4. Verify webhook URLs are publicly accessible
    Review your n8n webhook URL configuration in Settings > Webhooks, and check network/firewall rules to determine if these endpoints are reachable from untrusted networks
    Affected if Webhook URLs for the affected trigger nodes are exposed to the internet or untrusted networks

You are affected if your n8n version falls outside 2.25.7 or 2.26.2+ AND you have workflows using MicrosoftAgent365Trigger or StripeTrigger with exposed webhook URLs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.25.7 / 2.26.2 or later
Fixed in 2.25.72.26.2
Interim mitigation

Upgrade to n8n version 2.25.7 or 2.26.2 which implement proper request validation. Until then, restrict webhook URL exposure to trusted networks only.

Recommended fix High confidence

Upgrade to n8n 2.25.7 (if on 2.25.x line) or n8n 2.26.2 (if on 2.26.x line)

  1. Identify the current n8n version in use by checking the container/service configuration or running `n8n --version`
  2. If running version < 2.25.7: Upgrade to version 2.25.7
  3. If running version >= 2.26.0 and < 2.26.2: Upgrade to version 2.26.2
  4. After upgrading, verify the MicrosoftAgent365Trigger and StripeTrigger nodes are functioning correctly with proper webhook validation
  5. Review workflow executions to ensure legitimate payloads are being processed as expected

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in N8n Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54308 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-54308 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data