dbcve.org
N8nApplication

CVE-2026-44791

CRITICAL · 9.9 CVSS v3.1 Published 2026-06-23
Fix available
A fix is available. Upgrade to 1.123.43 / 2.20.7 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click 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 is an open source workflow automation platform. Prior to 1.123.43, 2.22.1, and 2.20.7, an authenticated user with permission to create or modify workflows could bypass the patch for CVE-2026-42232 in the XML node. When combined with other nodes, this could lead to RCE on the n8n host. This vulnerability is fixed in 1.123.43, 2.22.1, and 2.20.7.

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

This is a patch bypass for CVE-2026-42232 in n8n's XML node. An authenticated user with workflow creation/modification permissions can bypass the previous fix and achieve remote code execution by chaining the vulnerable XML node with other nodes. The vulnerability affects n8n versions prior to 1.123.43, 2.22.1, and 2.20.7.

MitigationUpgrade n8n to version 1.123.43, 2.22.1, or 2.20.7 to patch this vulnerability. Review existing workflows that use the XML node and restrict workflow creation/modification permissions to trusted users only until patching is complete.

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.43>= 2.0.0, < 2.20.7>= 2.21.0, < 2.22.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
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify installed n8n version
    Run the command to display the n8n server version (typically via the UI, CLI, or API endpoint that reports version info)
    Affected if The version is below 1.123.43, or between 2.0.0 and 2.20.7, or between 2.21.0 and 2.22.1
  2. Locate workflows using the XML node
    Search workflow configurations for instances of the XML node (often labeled as 'XML' or 'Read/Transform XML')
    Affected if Any workflow contains the XML node and the n8n instance is running an affected version
  3. Review user roles with workflow permissions
    Inspect the user management or access control settings to identify accounts granted workflow creation or modification permissions
    Affected if Untrusted or unauthorized users have workflow creation or modification access on an affected version
  4. Examine XML node configuration in workflows
    Inspect each workflow that uses the XML node to see if it is chained with other nodes that could enable code execution (such as code execution, HTTP request, or similar nodes)
    Affected if The XML node is chained with nodes that can execute code or make arbitrary network requests

You are affected if your n8n version falls within the vulnerable ranges AND untrusted users have workflow creation/modification permissions AND workflows containing the XML node exist on the instance.

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.43 / 2.20.7 / 2.22.1 or later
Fixed in 1.123.432.20.72.22.1
Interim mitigation

Upgrade n8n to version 1.123.43, 2.22.1, or 2.20.7 to patch this vulnerability. Review existing workflows that use the XML node and restrict workflow creation/modification permissions to trusted users only until patching is complete.

Recommended fix High confidence

1.123.43 (1.x) OR 2.22.1 (2.x >= 2.21.0) OR 2.20.7 (2.x < 2.21.0)

  1. 1. Identify the currently installed n8n version by checking the application or running 'n8n --version'
  2. 2. Determine which release branch you are on (1.x or 2.x) by reviewing your current version number
  3. 3. For 1.x users: Upgrade to version 1.123.43 or later
  4. 4. For 2.x users running >= 2.21.0: Upgrade to version 2.22.1 or later
  5. 5. For 2.x users running >= 2.0.0, < 2.21.0: Upgrade to version 2.20.7 or later
  6. 6. After upgrading, verify the XML node no longer allows XXE or external entity exploitation
  7. 7. Review workflow permissions to ensure only trusted users can create or modify workflows

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

Fix this in N8n Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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