All vulnerabilities
CVE-2026-86076GHSA-hw8v-xxg5-vvvx

n8n: Expression Sandbox Escape in Editor-UI Enables Stored Cross-User JavaScript Execution

n8n-io n8nnpmFrameworks
CVSS
8.7High
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.79%Chance of exploitation activity in the next 30 days, higher than 55% of CVEs. Scored 24 Oct 2026FIRST EPSS
Fixed in1.123.76Also 2.38.2, 2.37.7OSV
Published8 Sep 2026Updated 10 Sep 2026CVE List

What fixes it

  • 1.123.76n8n, npmOSVnpm install n8n@1.123.76
  • 2.38.2n8n, npmOSVnpm install n8n@2.38.2
  • 2.37.7n8n, npmOSVnpm install n8n@2.37.7

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Timeline

  1. 8 Sep 2026, 21:28 UTCPublishedCVE List
  2. 24 Oct 2026, 23:56 UTCExploit code publicGitHub proof-of-concept repositories

Reports 1

1 outlet mention it. Reports are not confirmation; each links to its source.

Description

n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the expression compiler sanitizer resolved through dynamically scoped this and did not reject reserved class member names. A class field named __sanitize could rebind the sanitizer and reach the Function constructor, enabling backend code execution and editor-preview JavaScript execution. The affected AST hook is PrototypeSanitizer in packages/workflow/src/expression-sandboxing.ts. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.

Text from CVE List

Affected versions 6

  • n8naffected: >= 2.38.0, < 2.38.2CVE List
  • n8naffected: >= 2.0.0, < 2.37.7CVE List
  • n8naffected: < 1.123.76CVE List
  • n8n, npmfrom first release, fixed in 1.123.76OSV
  • n8n, npmfrom 2.38.0, fixed in 2.38.2OSV
  • n8n, npmfrom 2.0.0, fixed in 2.37.7OSV

References 4