| Package | Affected versions | Patched versions |
|---|---|---|
| n8n | = 2.32.0≥ 2.31.0, < 2.31.5< 1.123.67 | 2.31.51.123.67 |
| n8n | ≥ 2.0.0-rc.0, < 2.31.5≥ 2.32.0, < 2.32.1< 1.123.67 | 2.31.52.32.11.123.67 |
The Edit Fields (Set) node assigned output fields through a dot-notation path setter without restricting the field name, so an authenticated user could name a field after an inherited built-in method path and corrupt a shared global in the main Node.js process. Because that global was used on the request-authentication path, the instance then failed every authenticated request, causing a instance-wide denial of service for all users until the process was restarted.
The issue has been fixed in n8n versions 1.123.67, 2.31.5, and 2.32.1. Users should upgrade to one of these versions or later to remediate the vulnerability.
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free