dbcve.org
N8nApplication

CVE-2026-33696

HIGH · 8.8 CVSS v3.1 Published 2026-03-25
Fix available
A fix is available. Upgrade to 1.123.27 / 2.13.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 2.14.1, 2.13.3, and 1.123.27, an authenticated user with permission to create or modify workflows could exploit a prototype pollution vulnerability in the XML and the GSuiteAdmin nodes. By supplying a crafted parameters as part of node configuration, an attacker could write attacker-controlled values onto `Object.prototype`. An attacker could use this prototype pollution to achieve remote code execution on the n8n instance. The issue has been fixed in n8n versions 2.14.1, 2.13.3, and 1.123.27. Users should upgrade to one of these versions or later to remediate the vulnerability. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only, and/or disable the XML node by adding `n8n-nodes-base.xml` to the `NODES_EXCLUDE` environment variable. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

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

Authenticated users with workflow edit permissions can exploit prototype pollution in the XML and GSuiteAdmin nodes by supplying crafted parameters in node configuration, allowing arbitrary values to be written to Object.prototype and potentially achieving remote code execution.

MitigationUpgrade n8n to version 2.14.1, 2.13.3, or 1.123.27 or later. If immediate upgrade is not feasible, limit workflow creation/editing to trusted users and/or disable the XML node via NODES_EXCLUDE environment variable as short-term mitigation.

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.27>= 2.0.0, < 2.13.3= 2.14.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Check n8n version
    Run 'n8n --version' or check the version in the UI footer /api/health endpoint
    Affected if Version is less than 1.123.27, or between 2.0.0 and 2.13.3 exclusive, or exactly 2.14.0
  2. Verify if XML node is enabled
    Check the NODES_EXCLUDE environment variable; if set, ensure XML node is listed; if not set, XML node is enabled by default
    Affected if XML node is enabled (not excluded via NODES_EXCLUDE) and version is in affected range
  3. Verify if GSuiteAdmin node is enabled
    Check if GSuiteAdmin node appears in the node list in the n8n UI under the Google category
    Affected if GSuiteAdmin node is available and version is in affected range
  4. Review workflow permissions
    Check user roles and permissions in n8n: go to Settings > Users or inspect IAM/SSO configuration for users with workflow create/modify rights
    Affected if Any user账户拥有workflow创建或修改权限(而非仅受信任的管理员)
  5. Audit node configurations for prototype pollution patterns
    Export workflows and inspect XML/GSuiteAdmin node configurations for unexpected __proto__, constructor, or prototype properties in parameter values
    Affected if Found node configurations with suspicious property names that could indicate attempted exploitation

If n8n version is in the affected range AND (XML or GSuiteAdmin nodes are enabled) AND users with workflow permissions exist, the environment is potentially vulnerable to prototype pollution exploitation.

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.27 / 2.13.3 or later
Fixed in 1.123.272.13.3
Interim mitigation

Upgrade n8n to version 2.14.1, 2.13.3, or 1.123.27 or later. If immediate upgrade is not feasible, limit workflow creation/editing to trusted users and/or disable the XML node via NODES_EXCLUDE environment variable as short-term mitigation.

Recommended fix High confidence

Upgrade to n8n version 2.14.1 (or 2.13.3 for 2.x branch, or 1.123.27 for 1.x branch)

  1. Back up the n8n instance data and configuration before proceeding with the upgrade
  2. Stop the n8n service to prevent any active connections during the upgrade
  3. Upgrade n8n to version 2.14.1 (or 2.13.3 if staying on 2.x branch, or 1.123.27 if staying on 1.x branch) using the installation method previously used (npm, Docker, or binary)
  4. For npm installations: Run `npm install -g [email protected]` or `npm install -g [email protected]` or `npm install -g [email protected]`
  5. For Docker: Update the image tag to `n8nio/n8n:2.14.1` or the appropriate version
  6. For binary installations: Download and install the new version from the n8n releases
  7. Verify the upgrade was successful by checking the n8n version after restart
  8. Restart the n8n service
Caveat Review n8n release notes for any breaking changes between your current version and the target version before upgrading

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
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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