Zero Day Monitor
DashboardVulnerabilitiesTrendingZero-DaysNews
Login
ImpressumPrivacy Policy
Zero Day Monitor © 2026
1886 articles · 106953 vulns · 38/55 feeds (7d)
← Back to list
—
CVE-2026-33696EXPLOITED
n8n-io · n8n

n8n Vulnerable to Prototype Pollution in XML & GSuiteAdmin node parameters lead to RCE

Description

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.

Affected Products

VendorProductVersions
n8n-ion8n< 1.123.27, >= 2.0.0-rc.0, < 2.13.3, = 2.14.0

References

  • https://github.com/n8n-io/n8n/security/advisories/GHSA-mxrg-77hm-89hv(x_refsource_CONFIRM)

Related News (1 articles)

Tier C
VulDB4h ago
CVE-2026-33696 | n8n-io n8n up to 1.123.26/2.13.2/2.14.0 Parameter NODES_EXCLUDE prototype pollution (GHSA-mxrg-77hm-89hv)
→ No new info (linked only)
CISA KEV❌ No
Actively exploited✅ Yes
CWECWE-1321
Published3/25/2026
Last enriched4h agov2
Trending Score35
Source articles1
Independent1
Info Completeness7/14
Missing: cvss, epss, kev, exploit, patch, iocs, mitre_attack

Community Vote

0
Login to vote
0 upvotes0 downvotes
No votes yet

Pin to Dashboard

Verification

State: unverified
Confidence: 0%

Version History

v2
Last enriched 4h ago
v2Tier C4h ago

Updated severity to CRITICAL, marked as actively exploited, and provided a more detailed description of the vulnerability.

descriptionseverityactivelyExploited
via VulDB
v14h ago

Initial creation