dbcve.org
N8nApplication

CVE-2026-25054

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-04
Fix available
A fix is available. Upgrade to 1.123.9 / 2.2.1 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 versions 1.123.9 and 2.2.1, a Cross-Site Scripting (XSS) vulnerability existed in a markdown rendering component used in n8n's interface, including workflow sticky notes and other areas that support markdown content. An authenticated user with permission to create or modify workflows could abuse this to execute scripts with same-origin privileges when other users interact with a maliciously crafted workflow. This could lead to session hijacking and account takeover. This issue has been patched in versions 1.123.9 and 2.2.1.

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 (XSS) vulnerability exists in n8n's markdown rendering component used for workflow sticky notes and other markdown-supported areas. Authenticated users with workflow edit permissions can inject malicious scripts that execute in the browsers of other users who view the crafted workflow, enabling session hijacking and account takeover.

MitigationUpgrade n8n to version 1.123.9 or 2.2.1 or later. If immediate upgrade is not feasible, limit workflow creation/modification permissions to trusted users 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:< 1.123.9>= 2.0.0, < 2.2.1

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 the command 'n8n --version' from the command line, or access the n8n UI and navigate to Settings > About, or check the package.json file in the n8n installation directory
    Affected if The version is below 1.123.9, or is 2.0.0 through 2.2.0 (inclusive)
  2. Verify markdown feature usage
    Review existing workflows in the n8n UI and check if any workflows contain sticky notes with markdown content, or check database tables for workflow sticky note entries containing markdown syntax
    Affected if Workflows exist with sticky notes or markdown-supported content that could contain injected scripts
  3. Identify workflow edit permission scope
    Review user roles and permissions in n8n under Settings > Users, or query the database for users with workflow create or edit permissions
    Affected if Multiple users or untrusted users have workflow edit or create permissions, increasing the likelihood of malicious injection
  4. Inspect stored sticky note content
    Query the workflow database table for sticky note fields and examine the stored HTML/markdown content for suspicious script tags, iframe elements, or event handlers (onclick, onload, etc.)
    Affected if Any sticky note entries contain unescaped HTML script tags or JavaScript event handlers

A user is affected if their n8n installation version is less than 1.123.9 or between 2.0.0 and 2.2.0 inclusive, and workflows with sticky notes are in use by users with edit permissions.

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.9 / 2.2.1 or later
Fixed in 1.123.92.2.1
Interim mitigation

Upgrade n8n to version 1.123.9 or 2.2.1 or later. If immediate upgrade is not feasible, limit workflow creation/modification permissions to trusted users only.

Recommended fix High confidence

Upgrade to n8n version 1.123.9 (for 1.x users) or version 2.2.1 (for 2.x users) or later

  1. 1. Backup your n8n installation and database before upgrading
  2. 2. Identify your current n8n version (check via UI or CLI: n8n --version)
  3. 3. If running version 1.x (< 1.123.9): Upgrade to version 1.123.9 or later (e.g., npm install [email protected] or docker pull n8nio/n8n:1.123.9)
  4. 4. If running version 2.x (>= 2.0.0 and < 2.2.1): Upgrade to version 2.2.1 or later (e.g., npm install [email protected] or docker pull n8nio/n8n:2.2.1)
  5. 5. Restart the n8n service after upgrading
  6. 6. Verify the new version is running and test workflow functionality
Caveat Upgrading from n8n 1.x to 2.x may introduce breaking changes; review n8n's migration guide for version 2.0 before upgrading across major versions

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

Fix this in N8n Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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