Skip to main content
VulnerabilityPublished Updated

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

Affects n8nSource GCVE Database

0
Authoritative record:CVE-2026-42236· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 1.123.32 soon.

Data as of 27 Oct 2026, 00:07 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.123.32, 2.18.1, 2.17.4
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade n8n to 1.123.32; n8n to 2.18.1; n8n to 2.17.4.

Affected software

ProductAffectedFixed in
npmn8nAffected
  • <1.123.32
Fixed in
  • 1.123.32
npmn8nAffected
  • >=2.18.0 <2.18.1
Fixed in
  • 2.18.1
npmn8nAffected
  • >=2.0.0 <2.17.4
Fixed in
  • 2.17.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

## 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.

References

Community reviews

Loading reviews…