INCIDENT MAP

Browse / AI Framework and Platform Flaws / CVE-2026-59206

n8n: Prototype Pollution via Workflow Credentials Leads to Unauthenticated User and Project Enumeration

CVE-2026-59206 ยท 2026-07-22 high

Class
AI Framework and Platform Flaws (filed by a model that read the advisory)
Technique
Authentication and access control
Affected
n8n (npm)
Gets past
Authentication check
CVSS
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:L/SI:L/SA:N
EPSS
0.7% chance of exploitation in 30 days

How it works, in short

A user with workflow create rights saves a workflow with prototype-polluting keys, so later unauthenticated requests are treated as privileged and user data is exposed. (Our summary, written by a model. The source text is below.)

Details

Impact

An authenticated user with the default workflow:create permission could pollute Object.prototype through a crafted workflow saved, updated, or imported via the workflow API. This can be leveraged to bypass authentication, allowing unauthenticated requests to be treated as a privileged user and exposing endpoints such as the user and project listings. As a result, every account's personal data (email, role, MFA status) and all projects on the instance may be disclosed to unauthenticated callers. The pollution can also corrupt global state, making parts of the instance unresponsive until restarted.

Patches

The issue has been fixed in n8n versions 1.123.61, 2.27.4, and 2.28.1. Users should upgrade to one of these versions or later to remediate the vulnerability.

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict workflow creation and editing permissions to fully trusted users only. - Restrict network access to the n8n instance to trusted users only.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

References

Source: GitHub Advisory Database, used under CC BY 4.0.