CVE-2026-54302
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 · uneditedn8n is an open source workflow automation platform. Prior to 1.123.55, 2.25.7, and 2.26.2, an authenticated user with workflow edit access could inject arbitrary JavaScript into the Chat Trigger's generated page by setting a malicious webhookId. When a logged-in user visited the chat URL, the injected code executed in the n8n origin with that user's session privileges. This vulnerability is fixed in 1.123.55, 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 confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in n8n's Chat Trigger feature. An authenticated user with workflow edit permissions can inject malicious JavaScript into the webhookId parameter, which then executes in the browser of any logged-in user who visits the generated chat URL, inheriting that user's session privileges.
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< 1.123.55>= 2.0.0, < 2.25.7>= 2.26.0, < 2.26.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify n8n installation versionLog into the n8n UI and locate the version number typically displayed in the footer or header of the interface. Alternatively, check via command line if self-hosted: 'docker ps' or check package.json/package-lock.json in the installation directory.Affected if The installed version falls into any of these ranges: < 1.123.55, >= 2.0.0 and < 2.25.7, or >= 2.26.0 and < 2.26.2.
-
Confirm Chat Trigger feature is in useNavigate to the Workflows section in the n8n UI and review the trigger nodes used in each workflow. Look for workflows that use the Chat trigger node type.Affected if Any workflow exists that utilizes the Chat Trigger node, creating a publicly accessible chat URL.
-
Inspect Chat Trigger node configurationOpen a workflow containing a Chat Trigger node and examine the node settings. Specifically, locate the webhookId field within the Chat Trigger configuration panel.Affected if The webhookId field contains unexpected characters or appears to have been manually modified from its default generated value, indicating potential injection.
-
Review recent workflow modificationsCheck the workflow history or audit logs for recent edits to workflows containing Chat Trigger nodes, focusing on changes made by users with workflow edit permissions.Affected if A user with workflow edit permissions recently modified a Chat Trigger workflow, and the modification included script-like content in the webhookId parameter.
-
Verify chat URL accessibilityIf a Chat Trigger workflow is active, access its generated chat URL (typically /chat/<webhookId>) and examine whether the page loads without errors or displays unexpected behavior.Affected if Visiting the generated chat URL triggers JavaScript execution in the browser, such as unexpected popups, script loading, or console errors indicating XSS.
You are affected if your n8n version is below 1.123.55, between 2.0.0-2.25.6, or between 2.26.0-2.26.1 AND you have active workflows using the Chat Trigger feature that could be exploited by an authenticated user with edit permissions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.123.552.25.72.26.2
Upgrade n8n to version 1.123.55, 2.25.7, or 2.26.2 or later to patch the vulnerable Chat Trigger component. Alternatively, restrict workflow edit access to trusted administrators only until the upgrade can be performed.
1.123.55 (for v1.x) or 2.25.7/2.26.2 (for v2.x, depending on your current version)
- 1. Backup your n8n instance (database, credentials, and configuration files)
- 2. Identify your current n8n version using `n8n --version` or your deployment method
- 3. If running version < 1.123.55, upgrade to version 1.123.55
- 4. If running version >= 2.0.0 and < 2.25.7, upgrade to version 2.25.7
- 5. If running version >= 2.26.0 and < 2.26.2, upgrade to version 2.26.2
- 6. Restart the n8n service after upgrading
- 7. Verify the upgrade was successful and test Chat Trigger functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54302 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-54302 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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