dbcve.org
N8nApplication

CVE-2026-54303

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-23
Fix available
A fix is available. Upgrade to 2.24.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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.24.0, an endpoint in the Meta and Microsoft Teams trigger nodes reflects a query parameter into the HTTP response without sanitization or Content-Security-Policy headers, enabling reflected XSS in the n8n origin when a logged-in user visits a crafted URL. This vulnerability is fixed in 2.24.0.

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

Reflected XSS vulnerability in n8n workflow automation platform versions prior to 2.24.0. The Meta and Microsoft Teams trigger nodes reflect query parameters into HTTP responses without sanitization or Content-Security-Policy headers, allowing attackers to inject malicious scripts via crafted URLs targeting logged-in users.

MitigationUpgrade n8n to version 2.24.0 or later, which implements proper input sanitization and adds Content-Security-Policy headers to prevent reflected XSS.

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.24.0

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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. Determine installed n8n version
    Run `n8n --version` from command line, check the UI footer, or query the API endpoint `/rest/version`
    Affected if The installed version is below 2.24.0
  2. Check for Meta trigger node usage
    Search workflow files or database for nodes of type `n8n-nodes-base.metaTrigger` or look for workflows containing the Meta trigger node in the n8n UI
    Affected if Any active workflow uses the Meta trigger node and the n8n version is below 2.24.0
  3. Check for Microsoft Teams trigger node usage
    Search workflow files or database for nodes of type `n8n-nodes-base.microsoftTeamsTrigger` or look for workflows containing the Microsoft Teams trigger node in the n8n UI
    Affected if Any active workflow uses the Microsoft Teams trigger node and the n8n version is below 2.24.0
  4. Verify Content-Security-Policy header presence
    Send a test request to the n8n instance and inspect response headers for `Content-Security-Policy` header
    Affected if The CSP header is absent and the version is below 2.24.0 with affected trigger nodes configured

You are affected if running n8n version below 2.24.0 with Meta or Microsoft Teams trigger nodes actively configured in any workflow and the application does not send Content-Security-Policy headers.

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.24.0 or later
Fixed in 2.24.0
Interim mitigation

Upgrade n8n to version 2.24.0 or later, which implements proper input sanitization and adds Content-Security-Policy headers to prevent reflected XSS.

Recommended fix High confidence

2.24.0

  1. Identify your current n8n deployment method (Docker, npm, or binary)
  2. Stop the n8n service
  3. For Docker: Run 'docker pull n8nio/n8n:2.24.0' to pull the fixed image, then restart the container
  4. For npm: Run 'npm install [email protected]' to install the fixed version
  5. For binary: Download the n8n 2.24.0 binary from the official releases
  6. Start the n8n service
  7. Verify the upgrade was successful by checking the n8n version

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-54303 — 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-54303 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