CVE-2026-77069

Medium

Description

n8n before 1.123.69, 2.33.4, and 2.34.1 contains an SSRF protection bypass in the OAuth2 credential authorization-code-to-access-token exchange. While OAuth2 discovery and dynamic-client-registration requests use n8n's SSRF-protected HTTP client, the token exchange uses a separate client with no SSRF guard. A user with credential-creation permissions can set the access-token URL to an internal address and complete the OAuth2 flow, causing n8n to send a fixed-shape token-exchange POST to that target and reflect its response body back to the attacker (limited to what the target returns to this specific request).

SeverityMedium
CVSS4.3
Exploit probability—
ProductN8n
PublishedAug 20, 2026
First seenAug 20, 2026

How to fix

Update
  • n8n n8n1.123.69, 2.33.4 or later

Affected products

ProductAffected versionsFixed in
n8n n8nv < 1.123.69, 2.33.0 ≤ v < 2.33.4, 2.34.01.123.69, 2.33.4

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.