The vulnerability exists in the Code node’s JavaScript virtual machine within the workflow platform. In pre‑1.123.69, 2.33.4, and 2.34.1 releases, the sandbox did not freeze Function.prototype, allowing an authenticated user who can create workflows to inject code that mutates this prototype during execution. By doing so the attacker can gain a reference to the host’s globalThis object, which effectively breaks the isolation boundary and permits arbitrary code execution on the host environment. The danger is pronounced because the payload is delivered inside an authenticated workflow execution channel, bypassing typical web boundaries.

n8n‑io’s n8n automation platform is affected. The flaw appears in all releases older than version 1.123.69, 2.33.4, and 2.34.1. Users running any of these legacy builds are susceptible until an update is applied.

The CVSS score of 6 indicates a moderate severity, and EPSS data is not available, so actual exploitation probability is uncertain. The vulnerability is not listed in the CISA KEV catalog, suggesting no publicly known attacks yet. The exploit chain requires that the deployment’s configuration allows certain modules to be imported through the allowlist; an attacker must also have credentials that grant the right to create and run workflows. Given these prerequisites, the risk level is moderate but non‑negligible, and a patch is strongly recommended.