CVE-2026-59206: n8n: Prototype Pollution via Workflow Credentials Leads to Unauthenticated User and Project Enumeration

Published Jul 9, 2026
·
Updated

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.

Other sources

n8n is an open source workflow automation platform. Prior to 1.123.61, 2.27.4, and, 2.28.1, 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, allowing unauthenticated requests to be treated as a privileged user and exposing user and project listing endpoints. This issue is fixed in versions 1.123.61, 2.27.4, and 2.28.1.

NVD

Affected Software

7 affected componentsFixes available
n8n<1.123.61, <2.27.4, <2.28.1
n8n N8n Node.js<1.123.61
n8n N8n Node.js>=2.0.0<2.27.4
n8n N8n Node.js=2.28.0
npm/n8n>=2.0.0-rc.0<2.27.4
2.27.4
npm/n8n>=2.28.0<2.28.1
2.28.1
npm/n8n<1.123.61
1.123.61

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 2.27.4
  2. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 2.28.1
  3. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 1.123.61
  4. Upgrade

    Upgrade n8n to a version that resolves this vulnerability.

    Fixed in 1.123.61
  5. Upgrade

    Upgrade n8n to a version that resolves this vulnerability.

    Fixed in 2.27.4
  6. Upgrade

    Upgrade n8n to a version that resolves this vulnerability.

    Fixed in 2.28.1
  7. Compensating control

    Restrict network access to the n8n instance to trusted users only (short-term mitigation if upgrading is not immediately possible).

  8. Compensating control

    Restrict workflow creation and editing permissions to fully trusted users only (short-term mitigation if upgrading is not immediately possible).

Event History

Jul 9, 2026
CVE Published
via MITRE·03:30 PM
Data Sourced
via MITRE·03:30 PM
DescriptionWeakness
Data Sourced
via NVD·04:16 PM
DescriptionSeverityWeaknessAffected Software
Jul 22, 2026
Advisory Published
via GitHub·09:57 PM
Data Sourced
via GitHub·09:57 PM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-59206?

The severity of CVE-2026-59206 is rated at 56.

2

How do I fix CVE-2026-59206?

To mitigate CVE-2026-59206, upgrade n8n to versions 1.123.61, 2.27.4, or 2.28.1.

3

What impact does CVE-2026-59206 have on n8n users?

CVE-2026-59206 allows authenticated users to exploit prototype pollution, leading to unauthenticated user and project enumeration.

4

Who is affected by CVE-2026-59206?

CVE-2026-59206 affects n8n installations prior to versions 1.123.61, 2.27.4, and 2.28.1.

5

How can I determine if my n8n installation is vulnerable to CVE-2026-59206?

Check your n8n version against the patched releases; if it is below 1.123.61, 2.27.4, or 2.28.1, your installation is vulnerable.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203