Quick answers
- Is CVE-2026-72765 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-72765 being exploited in the wild.
- How severe is CVE-2026-72765?
- Critical severity, with a CVSS score of 9.9, published 11 August 2026.
- Which products and versions are affected?
- N8n all versions before 2.31.5 and 2.32.1.
- Is there a fix for CVE-2026-72765?
- A patch was published on 2026-07-22: Fixed in n8n 2.31.5 and 2.32.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-72765 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-72765?
- Check whether you run N8n at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This is a sandbox escape vulnerability in n8n's expression evaluation engine (CWE-94: Code Injection). The root cause is improper validation of arrow function bodies in expressions, allowing an attacker to break out of the intended sandbox context. An authenticated user with workflow creation/modification permissions can craft malicious expressions using arrow functions to gain unauthenticated remote code execution on the underlying host. The attack requires authentication and workflow edit permissions but no user interaction. The vulnerability has been patched in n8n versions 2.31.5 and 2.32.1.
Affected products
- n8n n8n all versions before 2.31.5 and 2.32.1
Identifiers
- CVE-2026-72765
- GHSA-gv7g-jm28-cr3m
Timeline
- 2026-07-22: disclosed: Vulnerability disclosed via GitHub Security Advisory GHSA-gv7g-jm28-cr3m
- 2026-07-22: patched: Fixed in n8n 2.31.5 and 2.32.1