{"items":[{"id":"NVI-00016173","kind":"vulnerability","title":"n8n: Prototype Pollution via Dot-Notation Field Names Leads To Instance-Wide Denial of Service","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-xwx6-jjhv-84p8"],"plain_summary":"GitHub lists this reviewed advisory for n8n, n8n, n8n. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-39d5c1f8e3a309b4399d6cc6394a3c7b"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-39d5c1f8e3a309b4399d6cc6394a3c7b","url":"https://github.com/advisories/GHSA-xwx6-jjhv-84p8","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-xwx6-jjhv-84p8","publisher":"GitHub Advisory Database","observed_at":"2026-11-03T17:42:43.803Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-39d5c1f8e3a309b4399d6cc6394a3c7b"],"technology":"n8n","known_exclusions":[],"conditions_summary":"## Impact\n\nThe 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.\n\n## Patches\n\nThe 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.\n\n## Workarounds\n\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Restrict n8n instance access to fully trusted users only.\n- Disable or restrict workflow creation and execution permissions for untrusted users.\n- Monitor for unexpected process-wide HTTP 500 errors and restart the process promptly if they occur.\n\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.","public_affected_ranges":["< 1.123.67"]},{"certainty":"source_listed","source_ids":["sr-39d5c1f8e3a309b4399d6cc6394a3c7b"],"technology":"n8n","known_exclusions":[],"conditions_summary":"## Impact\n\nThe 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.\n\n## Patches\n\nThe 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.\n\n## Workarounds\n\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Restrict n8n instance access to fully trusted users only.\n- Disable or restrict workflow creation and execution permissions for untrusted users.\n- Monitor for unexpected process-wide HTTP 500 errors and restart the process promptly if they occur.\n\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.","public_affected_ranges":[">= 2.32.0, < 2.32.1"]},{"certainty":"source_listed","source_ids":["sr-39d5c1f8e3a309b4399d6cc6394a3c7b"],"technology":"n8n","known_exclusions":[],"conditions_summary":"## Impact\n\nThe 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.\n\n## Patches\n\nThe 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.\n\n## Workarounds\n\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Restrict n8n instance access to fully trusted users only.\n- Disable or restrict workflow creation and execution permissions for untrusted users.\n- Monitor for unexpected process-wide HTTP 500 errors and restart the process promptly if they occur.\n\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.","public_affected_ranges":[">= 2.0.0-rc.0, < 2.31.5"]}],"null_published_at":"2026-11-04T10:04:27.901Z","source_updated_at":"2026-07-22T22:12:34.000Z","source_disclosed_at":"2026-07-22T22:12:33.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-03T17:42:43.803Z"}],"next_cursor":null,"snapshot_revision":"42594"}