n8nGHSA-cw9w-vv67-hf73

n8n: Per-Resource OAuth Consent Bypass via Unbound Refresh Token Resource Substitution

CVE-2026-86073 · Published Sep 10, 2026

Medium

Fix: upgrade to 2.37.7 or later (2 fixed versions below)

Impact

The OAuth token endpoint bound an authorization code's first access token to the consented resource, but not its refresh token. Refreshing only checked that the requested resource was registered, not that it matched the original grant. An OAuth client approved for one workflow could refresh with a different workflow's URL and get a valid, unapproved token for it. The patch binds refresh tokens to the granted resource and rejects mismatches.

Exploitation requires the attacker to register an OAuth client, convince an authenticated user to approve that client for one known protected resource, and know the URL of a second protected resource that the consenting user is permitted to execute.

Patches

The issue has been fixed in n8n versions 2.38.1 and 2.37.7. Users should upgrade to this version or later to remediate the vulnerability.

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

Restrict n8n instance access to fully trusted users only.
Deactivate MCP Trigger, form, and webhook workflows that are protected by the n8n OAuth server if they are not required.
Audit connected OAuth clients and revoke any that are not recognized or no longer needed.
Require re-authorization for all existing OAuth clients after upgrading, as previously issued refresh tokens did not store the original...

Affected versions

Package	Affected	Fixed in
n8n npm	>= 2.38.0, < 2.38.1	2.38.1
	< 2.37.7	2.37.7

Details and references

## Impact The OAuth token endpoint bound an authorization code's first access token to the consented resource, but not its refresh token. Refreshing only checked that the requested resource was registered, not that it matched the original grant. An OAuth client approved for one workflow could refresh with a different workflow's URL and get a valid, unapproved token for it. The patch binds refresh tokens to the granted resource and rejects mismatches. Exploitation requires the attacker to register an OAuth client, convince an authenticated user to approve that client for one known protected resource, and know the URL of a second protected resource that the consenting user is permitted to execute. ## Patches The issue has been fixed in n8n versions 2.38.1 and 2.37.7. Users should upgrade to this version or later to remediate the vulnerability. ## Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict n8n instance access to fully trusted users only. - Deactivate MCP Trigger, form, and webhook workflows that are protected by the n8n OAuth server if they are not required. - Audit connected OAuth clients and revoke any that are not recognized or no longer needed. - Require re-authorization for all existing OAuth clients after upgrading, as previously issued refresh tokens did not store the original resource binding. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

CVSS 4.0: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N
Severity from: GitHub (reviewed advisory)
Weakness: CWE-863
Also known as: CVE-2026-86073

More n8n advisories

All n8n

MediumSep 10

n8n: Instance AI Credential Setup Accepts Unvalidated Probe URL from Fetched ContentCVE-2026-86074fixed in 2.37.7 +1 MediumSep 10

n8n: path traversalCVE-2026-86995fixed in 1.123.76 +2 MediumSep 10

n8n: missing authorizationCVE-2026-86085fixed in 2.37.7 +1 MediumSep 10

n8n: Log Streaming Event Destinations Decrypt Generic-Auth Credentials Without Ownership CheckCVE-2026-86993fixed in 1.123.76 +2 MediumSep 10

n8n: Disabled OIDC SSO Endpoints Remain Active and Issue Valid SessionsCVE-2026-86084fixed in 1.123.76 +2 MediumSep 10

n8n: GitHub Trigger 422 Reuse Path Skips Webhook Secret Storage, Causing Signature Verification to Fail-OpenCVE-2026-86080fixed in 1.123.76 +2