n8n: Prototype Pollution via Dot-Notation Field Names Leads To Instance-Wide Denial of Service
n8n contains a prototype pollution vulnerability in the Edit Fields (Set) node that allows an authenticated user to assign output fields using dot-notation paths without restricting field names. This can corrupt a shared global in the Node.js process, causing all authenticated requests to fail and resulting in an instance-wide denial of service until the process is restarted. The issue is fixed in versions 1.123.67, 2.31.5, and 2.32.1. Temporary mitigations include restricting access to trusted users and monitoring for HTTP 500 errors.
AI Analysis
Technical Summary
The vulnerability in n8n arises from the Edit Fields (Set) node assigning output fields through dot-notation path setters without validation of field names. An authenticated user can exploit this by naming a field after an inherited built-in method path, which corrupts a shared global variable in the main Node.js process. This shared global is used in the request-authentication path, causing all authenticated requests to fail and resulting in an instance-wide denial of service until the process is restarted. The vulnerability has been addressed in n8n versions 1.123.67, 2.31.5, and 2.32.1.
Potential Impact
An authenticated user can cause an instance-wide denial of service by corrupting a shared global variable used in request authentication. This leads to failure of all authenticated requests, disrupting service for all users until the n8n process is restarted.
Mitigation Recommendations
A fix is available 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 immediate upgrade is not possible, restrict instance access to fully trusted users, disable or restrict workflow creation and execution permissions for untrusted users, and monitor for unexpected HTTP 500 errors, restarting the process promptly if they occur. These workarounds are temporary and do not fully mitigate the risk.
n8n: Prototype Pollution via Dot-Notation Field Names Leads To Instance-Wide Denial of Service
Description
n8n contains a prototype pollution vulnerability in the Edit Fields (Set) node that allows an authenticated user to assign output fields using dot-notation paths without restricting field names. This can corrupt a shared global in the Node.js process, causing all authenticated requests to fail and resulting in an instance-wide denial of service until the process is restarted. The issue is fixed in versions 1.123.67, 2.31.5, and 2.32.1. Temporary mitigations include restricting access to trusted users and monitoring for HTTP 500 errors.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in n8n arises from the Edit Fields (Set) node assigning output fields through dot-notation path setters without validation of field names. An authenticated user can exploit this by naming a field after an inherited built-in method path, which corrupts a shared global variable in the main Node.js process. This shared global is used in the request-authentication path, causing all authenticated requests to fail and resulting in an instance-wide denial of service until the process is restarted. The vulnerability has been addressed in n8n versions 1.123.67, 2.31.5, and 2.32.1.
Potential Impact
An authenticated user can cause an instance-wide denial of service by corrupting a shared global variable used in request authentication. This leads to failure of all authenticated requests, disrupting service for all users until the n8n process is restarted.
Mitigation Recommendations
A fix is available 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 immediate upgrade is not possible, restrict instance access to fully trusted users, disable or restrict workflow creation and execution permissions for untrusted users, and monitor for unexpected HTTP 500 errors, restarting the process promptly if they occur. These workarounds are temporary and do not fully mitigate the risk.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-xwx6-jjhv-84p8
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a6150cc9c2644c7f8da012a
Added to database: 07/22/2026, 23:22:52 UTC
Last enriched: 07/22/2026, 23:26:51 UTC
Last updated: 07/22/2026, 23:26:51 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.