# CVE-2026-77083: n8n before 1.123.69 Code Node Sandbox Escape via Function.prototype Pollution

> Authenticated users can escape the Code node sandbox via prototype pollution to execute arbitrary code on the host, requiring specific module allowlists.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-2664-hr5v-554w, GHSA-c9c6-rq46-h25v, MINI-w726-g996-58r9

## What is CVE-2026-77083?

CVE-2026-77083 is a medium-severity code injection vulnerability in N8n N8n, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

n8n is a workflow automation platform. In versions prior to 1.123.69, 2.33.4, and 2.34.1, the JavaScript Code node's VM sandbox did not freeze the sandbox's Function.prototype, allowing an authenticated user with the ability to create and execute workflows to pollute it from within a Code node execution and recover a reference to the host's globalThis, resulting in a sandbox escape. The full exploit chain additionally depends on specific modules being available as allowlisted imports in the deployment's configuration. The issue is fixed in versions 1.123.69, 2.33.4, and 2.34.1.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2026-77083?

It affects 1 product.


Products: N8n N8n.

## How do I fix CVE-2026-77083?

Upgrade to a fixed version.

## Is CVE-2026-77083 being exploited?

There is no known exploitation of CVE-2026-77083 in the wild and no public exploit code.

## Other vulnerabilities in N8n N8n

- [CVE-2025-68613](https://insights.sbomify.com/CVE-2025-68613/): n8n Improper Control of Dynamically-Managed Code Resources (critical 10.0, exploited in the wild)
- [CVE-2026-21877](https://insights.sbomify.com/CVE-2026-21877/): n8n is vulnerable to Remote Code Execution via Arbitrary File Write (critical 10.0)
- [CVE-2026-21858](https://insights.sbomify.com/CVE-2026-21858/): n8n Vulnerable to Unauthenticated File Access via Improper Webhook Request Handling (critical 10.0)
- [CVE-2026-1470](https://insights.sbomify.com/CVE-2026-1470/): n8n Unsafe Workflow Expression Evaluation Allows Remote Code Execution (critical 9.9)
- [CVE-2025-68668](https://insights.sbomify.com/CVE-2025-68668/): n8n Vulnerable to Arbitrary Command Execution in Pyodide based Python Code Node (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77083 and fix it if it is affected.

What it is: CVE-2026-77083 is a medium-severity code injection vulnerability in N8n N8n, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-77083 in the wild and no public exploit code.

Affected product: N8n N8n. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-77083/ (Markdown: https://insights.sbomify.com/CVE-2026-77083/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-77083
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-77083
- OSV: https://osv.dev/vulnerability/CVE-2026-77083

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-77083/
Summaries are generated and may contain mistakes; the official description above is the record.