Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged n8n user
-
DeliverySave workflow with __proto__ connection key
-
ExploitPeriodic history-compaction task diffs connections
-
ExecutionBuilt-in Object prototype polluted process-wide
-
ImpactLogins and writes fail (denial of service)
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V3 - Web Frontend Security Prototype pollution prevention
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated low-privileged account with permission to create and save workflows (PR:L), and requires the workflow-history feature to be enabled (default), since the periodic workflow-history compaction task is what processes the connections object and triggers the prototype pollution. The specific trigger is a workflow connections key named with a reserved JavaScript property such as __proto__, constructor, or prototype. Limiting factors: exploitation is not possible by fully unauthenticated attackers, is neutralized by setting N8N_WORKFLOW_HISTORY_ENABLED=false where history is not needed, and is bounded to instances running n8n before 2.41.4 or 2.42.x before 2.42.1; restricting instance access to fully trusted users also limits exposure (per the vendor, these workarounds are temporary and do not fully remediate - upgrading is the complete fix). |
| Impact | The vuln.today priority is 'this_week' and the supplied CVSS 4.0 vector scores 7.1, but the real-world risk is moderate and gated by preconditions rather than critical. The vector is AV:N/AC:L/AT:N/PR:L/UI:N with impact VC:N/VI:L/VA:H - meaning network-reachable and low-complexity, but requiring an authenticated low-privileged account (PR:L) and yielding no confidentiality loss, only low integrity and high availability impact (a denial-of-service that breaks logins and writes). This is squarely a DoS/integrity issue, not data theft or code execution, so despite the 'high' severity band it is not a drive-by, unauthenticated catastrophe. No EPSS score was provided in the input, so exploitation probability cannot be quantified. The CVE is NOT in CISA KEV and no exploit/PoC code is referenced (only the vendor GHSA and VulnCheck advisories), so there is no evidence of active exploitation or published weaponized code. Net: a legitimate patch-this-week item for any multi-tenant or lower-trust n8n deployment because any user who can save a workflow can disrupt the whole instance, but lower urgency for single-admin or fully-trusted installations. Note the input Tags claim 'Information Disclosure', which conflicts with the CVSS impact (VC:N = no confidentiality impact) and the advisory title describing denial of service - treat the DoS characterization as authoritative. |
| Exploit ScenarioDerived | A low-privileged but authenticated n8n user creates and saves a workflow whose connections object contains a reserved key such as __proto__. When the periodic workflow-history compaction task later diffs that connections object, it pollutes the global Object prototype, after which the whole n8n process begins returning server errors for logins and writes - a denial of service affecting all users. No public exploit code is referenced in the available sources; exploitation requires only the ability to save a workflow. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
Prototype pollution in n8n allows an authenticated low-privileged user who can create and save workflows to corrupt built-in JavaScript object behaviour, which then causes logins and writes to fail with server errors across the instance. The flaw lives in the routine that diffs workflow connection sets: a connections key named with a reserved property such as __proto__, constructor, or prototype is used directly as an object member, and the periodic workflow-history compaction task later processes it, polluting the process-wide object prototype. Instances running n8n before 2.41.4 or 2.42.x before 2.42.1 are affected, workflow history is enabled by default, and no public exploit code was identified at time of analysis.
RemediationAI
Vendor-released patch: upgrade to n8n 2.41.4 or 2.42.1 (or later) from https://github.com/n8n-io/n8n/security/advisories/GHSA-fvv4-gmv9-xqf5. If upgrading is not immediately possible, the vendor lists three temporary mitigations that do not fully remediate the risk: restrict access to the n8n instance to fully trusted users only, which reduces the pool of accounts able to save a malicious workflow but does not remove existing stored payloads; set N8N_WORKFLOW_HISTORY_ENABLED=false where workflow history is not required, which prevents the compaction task from processing crafted connections at the cost of losing workflow version history; and audit existing workflows for connections containing reserved JavaScript property names such as __proto__, constructor, or prototype, removing or renaming them. The independent assessment stresses that upgrading is the complete fix and that the other measures are short-term only.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is the npm-distributed n8n workflow automation server, a Node.js application whose workflow definitions store node-to-node links in a 'connections' object that accepts arbitrary keys. Per the vendor advisory (GHSA-fvv4-gmv9-xqf5), the routine that diffs two sets of connections used those keys directly as object members, which is the classic CWE-1321 prototype pollution pattern: attacker-controlled property names such as __proto__, constructor, or prototype reach an assignment that walks onto Object.prototype instead of a locally scoped object. Because the polluted prototype lives for the lifetime of the Node.js process, the corruption is not confined to the malicious workflow but affects unrelated code paths, manifesting as failures in login and write handling. The trigger is asynchronous and indirect: it requires the periodic workflow-history compaction task to process the stored malicious workflow, which is why the vendor's mitigations centre on disabling workflow history (N8N_WORKFLOW_HISTORY_ENABLED=false) or auditing stored workflows for reserved property names in their connections. The provided CVSS 4.0 vector scores 7.1 with PR:L, UI:N, VC:N, VI:L and VA:H; the independent assessment scores it CVSS:3.1 7.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H), consistent with integrity and availability impact from an authenticated position. The supplied tags also list 'Information Disclosure', but the vendor advisory and the described impact characterise this as a denial-of-service condition rather than a data exposure; no disclosure mechanism is described in the available sources.
Know when Prototype Pollution gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
Network-reachable via saved workflow and low complexity, but needs an authenticated low-privileged account (PR:L); no confidentiality impact, minor integrity (failed writes), high availability impact from process-wide DoS.
Primary rating from Vendor (vulncheck).
CVSS VectorVendor: vulncheck
Lifecycle Timeline
2DescriptionCVE.org
n8n before 2.41.4 and 2.42.x before 2.42.1 contains a prototype pollution vulnerability that allows low-privileged users to alter built-in object behaviour by saving workflows with specially named connection keys. Attackers can add keys such as __proto__ to workflow connections, which the periodic history compaction task processes, causing logins and writes to fail with server errors.
Technical POC Analysis
CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes, i.e.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
The n8n workflow automation platform, versions before 2.41.4 and 2.42.x before 2.42.1, contains a high-severity prototype pollution flaw (CVE-2026-118678) that an authenticated low-privileged user can exploit to corrupt the instance's JavaScript runtime, causing logins and data writes to fail. This could lead to operational disruption and loss of automation continuity for teams relying on n8n, though no public exploit code has been identified at time of analysis. Leadership should prioritize remediation due to the potential for service unavailability and the likelihood of insider or compromised-account abuse.
No vendor-released patch identified at time of analysis. Interim mitigations include restricting workflow creation to trusted users, disabling workflow history if feasible, and closely monitoring authentication and write operations for failures; also consider network segmentation to limit lateral movement.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
More in Prototype Pollution
View allPrototype pollution in Adobe Acrobat Reader versions 24.001.30356, 26.001.21367 and earlier enables arbitrary code execu
All versions of package dojo are vulnerable to Prototype Pollution via the setObject function. Rated critical severity (
Prototype pollution in the farinspace Partners WordPress plugin (versions up to and including 0.2.0) enables remote unau
The package handlebars before 4.7.7 are vulnerable to Prototype Pollution when selecting certain compiling options to co
This affects the package ini before 1.3.6. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitabl
Prototype pollution vulnerability in 'deephas' versions 1.0.0 through 1.0.5 allows attacker to cause a denial of service
A Prototype Pollution issue in Cronvel Tree-kit v.0.7.4 and before allows a remote attacker to execute arbitrary code vi
A Prototype Pollution issue in Aliconnect /sdk v.0.0.6 allows an attacker to execute arbitrary code via the aim function
All versions of the package safe-eval are vulnerable to Prototype Pollution via the safeEval function, due to improper s
This affects the package vm2 before 3.9.4 via a Prototype Pollution attack vector, which can lead to execution of arbitr
Prototype Pollution in chargeover redoc v2.0.9-rc.69 allows attackers to execute arbitrary code or cause a Denial of Ser
alizeait unflatto <= 1.0.2 was discovered to contain a prototype pollution via the method exports.unflatto at /dist/inde
EUVD-2026-112384
GHSA-4v4v-jr32-r382
NVD
CVE.org
Exploit-DB