dbcve.org
N8nApplication

CVE-2026-56358

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 1.123.25 / 2.11.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable 8 weeks old

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 before 1.123.25 (1.x) and before 2.11.2 (2.x), with the fix also included in 2.12.0, contains a stored cross-site scripting vulnerability in the Form Trigger node's CSS sanitization that allows authenticated users to inject malicious scripts. Attackers with workflow creation permissions can inject XSS payloads that execute persistently for all form visitors, enabling form hijacking and phishing attacks.

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

A stored cross-site scripting vulnerability in n8n's Form Trigger node allows authenticated users with workflow creation permissions to inject malicious scripts through improper CSS sanitization, which executes persistently for all form visitors.

MitigationUpgrade n8n to version 1.123.25 (1.x series), 2.11.2 (2.x series), or 2.12.0 and later to patch the CSS sanitization in the Form Trigger node.

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:< 1.123.25>= 2.0.0, < 2.11.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
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 your n8n version
    Check the n8n UI footer for the version number, or query the /healthz API endpoint if self-hosted, or inspect the package.json file in the n8n installation directory
    Affected if The installed version is less than 1.123.25 for the 1.x series, or greater than or equal to 2.0.0 but less than 2.11.2 for the 2.x series
  2. Identify workflows using Form Trigger nodes
    Navigate to the n8n workflow list and search for workflows that contain the Form Trigger node, or query the workflows API endpoint for any workflows where the first node is of type 'n8n-nodes-base.formTrigger'
    Affected if Any workflow exists that uses the Form Trigger node, making the vulnerability applicable if the version is vulnerable
  3. Inspect Form Trigger node CSS configurations
    Open each workflow containing a Form Trigger node, edit the node, and examine the Form Field settings where custom CSS can be applied to form elements
    Affected if The Form Trigger contains custom CSS in any field configuration, as this is the attack surface for the sanitization flaw
  4. Review Form Trigger workflows for suspicious CSS patterns
    Examine the CSS values in the Form Trigger node fields for potential XSS payloads such as javascript: URLs, event handlers like onclick/onmouseover, or expression() constructs commonly used in CSS-based attacks
    Affected if Any CSS value in a Form Trigger contains executable script patterns or unusual URL schemes that could indicate exploitation

Your environment is affected if you are running a vulnerable n8n version (below 1.123.25 or between 2.0.0 and 2.11.2) AND you have any workflows using the Form Trigger node with custom CSS configured.

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 1.123.25 / 2.11.2 or later
Fixed in 1.123.252.11.2
Interim mitigation

Upgrade n8n to version 1.123.25 (1.x series), 2.11.2 (2.x series), or 2.12.0 and later to patch the CSS sanitization in the Form Trigger node.

Recommended fix High confidence

n8n 1.123.25 (for 1.x users) or n8n 2.11.2/2.12.0 (for 2.x users)

  1. For n8n 1.x users: Upgrade to version 1.123.25 or later
  2. For n8n 2.x users: Upgrade to version 2.11.2 or 2.12.0 or later
  3. After upgrading, verify the Form Trigger node's CSS sanitization is working correctly by testing existing forms

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

Fix this in N8n Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56358 — 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-56358 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