CVE-2026-86075: n8n: Unauthenticated Persistent Storage Exhaustion via OAuth Dynamic Client Registration Endpoint

Published Sep 8, 2026
·
Updated

n8n is an open source workflow automation platform. Prior to 2.37.7 and 2.38.2, the OAuth Dynamic Client Registration endpoint bounded redirecturis but accepted arbitrarily large clientname and granttypes values. An unauthenticated remote caller could repeatedly persist oversized values in oauthclients and exhaust database storage. The affected validation is in packages/cli/src/modules/oauth-server/oauth-server.service.ts, including MAXCLIENTNAMELENGTH and MAXGRANTTYPES. This issue is fixed in versions 2.37.7 and 2.38.2.

Affected Software

1 affected component
n8n n8n>0<=2.37.7, >=2.37.7<2.38.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade n8n to a version that resolves this vulnerability.

    Fixed in 2.37.7
  2. Upgrade

    Upgrade n8n to a version that resolves this vulnerability.

    Fixed in 2.38.2

Event History

Sep 8, 2026
CVE Published
via MITRE·09:29 PM
Data Sourced
via MITRE·09:29 PM
DescriptionWeakness

Frequently Asked Questions

1

Which deployments are exposed?

n8n versions before 2.37.7 and 2.38.2 are affected if their OAuth Dynamic Client Registration endpoint is reachable by unauthenticated remote callers.

2

What does an attacker need to exploit this issue?

An attacker does not need authentication. They need remote access to repeatedly submit dynamic client-registration requests containing oversized client_name or grant_types values.

3

What is the impact of successful exploitation?

Oversized registration values can be persistently stored in the oauth_clients database table. Repeated requests can exhaust available database storage.

4

What should be done if the instance cannot be upgraded immediately?

The provided information identifies the unauthenticated OAuth Dynamic Client Registration endpoint as the attack path. Restricting unauthenticated remote access to that endpoint can reduce exposure until upgrading to 2.37.7 or 2.38.2.

5

How can operators look for possible exploitation?

Review the oauth_clients table for unusually large client_name or grant_types values and investigate unexpected growth in database storage associated with OAuth client registrations.

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