Am I affected by n8n: Expression sandbox escape via arrow-function bodies enabling command execution? What should I do?
An authenticated user with permission to create or modify workflows could abuse crafted expressions using arrow functions to bypass the expression sandbox.
Affected: n8n < 2.31.5 and n8n >= 2.32.0, < 2.32.1. Fixed in: 2.31.5. What should you check, and what should you do about it?
Full incident page with sources: https://agentarmorhq.com/incidents/2026/07/ghsa-gv7g-jm28-cr3m-n8n (opens external site)
1 answer
Am I affected? Affected: n8n < 2.31.5 and n8n >= 2.32.0, < 2.32.1. Fixed in: 2.31.5.
- Check your version: run
npm ls n8n. Versions >= 2.32.0, < 2.32.1 of n8n are affected.
What to do now
- Upgrade to the fixed version: run
npm install n8n@2.32.1(first patched version 2.32.1). - Upgrade to n8n 2.31.5 or 2.32.1 or later.
- Restrict n8n instance access to fully trusted users only.
- Restrict workflow creation and editing permissions to fully trusted users only.
General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.
Sources
- GitHub Advisory Database: https://github.com/advisories/GHSA-gv7g-jm28-cr3m (opens external site)
Full incident page: https://agentarmorhq.com/incidents/2026/07/ghsa-gv7g-jm28-cr3m-n8n (opens external site)
Did this work for you?- Check your version: run