CVE-2026-77077 json
n8n before 1.123.69 Remote Code Execution via EventEmitter Prototype Pollution
published 3mo ago modified 2mo ago also EUVD-2026-63266 , GHSA-m3hg-p5r9-fg9h
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository n8n-io/n8n. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 7.6
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 47%
- public exploits
- 0
- none known
Summary
n8n versions before 1.123.69, 2.33.4, and 2.34.1 contain a JavaScript task runner VM sandbox escape. The runner's prototype-freezing routine covers globalThis functions but not internal module constructors such as EventEmitter, allowing an authenticated user with Code node access to exploit prototype pollution to execute arbitrary commands within the runner container. Because the polluted prototype is a process-wide object, the corruption persists across other tenants' Code node executions on the same shared runner. On v1.x instances without task runners enabled, Code node JavaScript runs directly in the main n8n process, where the impact could be higher.
Patch / fix
- npm n8n >= 1.123.69, >= 2.33.4, >= 2.34.1
- n8n-io n8n 1.123.69, 2.33.4, 2.34.1
Is CVE-2026-77077 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.56% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.2 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N |
| CNA | 4.0 | 7.2 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 7.6 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | n8n | <1.123.69 <2.34.1 <2.33.4 |
>= 1.123.69 >= 2.34.1 >= 2.33.4 |
Affected products
- n8n-io n8n
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
github.com
/n8n-io/n8n/security/advisories/GHSA-m3hg-p5r9-fg9h
vendor-advisory, mitigation, advisory
-
vulncheck.com
/advisories/n8n-before-remote-code-execution-via-eventemitter-prototype-pollution
third-party-advisory
Sources
- CVE List CVE-2026-77077
- NVD CVE-2026-77077
- Maintainer advisory GHSA-m3hg-p5r9-fg9h
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of n8n-io/n8n published their own advisory on GitHub. Reviewed sources take precedence over it.