Free AI Safety Workshop — in collaboration with explainx.aiSave your seat
AgentbeamBeta
AI agent vulnerability · n8n

CVE-2026-42236: n8n Vulnerable to Unauthenticated Denial of Service via MCP Client Registration

highCVSS 4.0 8.7 · 3.1 7.5GHSA-49m9-pgww-9vq6

Impact The MCP OAuth client registration endpoint accepted unauthenticated requests and stored client data without adequate resource controls. An unauthenticated remote attacker could exhaust server memory resources by sending large registration payloads, rendering the n8n instance unavailable.

Published Apr 29, 2026 · Updated May 8, 2026

Affected packages

n8n

Ecosystem
npm
Affected
< 1.123.32
Fixed in
1.123.32
Check
npm ls n8n

n8n

Ecosystem
npm
Affected
>= 2.18.0, < 2.18.1
Fixed in
2.18.1
Check
npm ls n8n

n8n

Ecosystem
npm
Affected
>= 2.0.0, < 2.17.4
Fixed in
2.17.4
Check
npm ls n8n

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

The MCP OAuth client registration endpoint accepted unauthenticated requests and stored client data without adequate resource controls. An unauthenticated remote attacker could exhaust server memory resources by sending large registration payloads, rendering the n8n instance unavailable. The MCP enable/disable toggle gates MCP access but did not restrict client registrations, meaning the endpoint is reachable regardless of whether MCP access is enabled on the instance.

The patches address the unbound registration with an upper bound of registered clients and disabling creation when MCP is disabled on the instance. Mean to restrict the payload size of requests already exist and can be used to control additional risks.

Patches

The issue has been fixed in n8n versions 1.123.32, 2.17.4, and 2.18.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 network access to the n8n instance to prevent requests from untrusted sources.
  • Reduce the maximum accepted payload size by lowering the N8N_PAYLOAD_SIZE_MAX environment variable from its default value.

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

Credited to ori-ron.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More n8n vulnerabilities

All n8n entries