CVE-2026-77069

Published: Ago 20, 2026 Last Modified: Ago 20, 2026
ExploitDB:
Other exploit source:
Google Dorks:
LOW 2,3
Source: [email protected]
Attack Vector: network
Attack Complexity: low
Privileges Required: low
User Interaction: none
Confidentiality: N/A
Integrity: N/A
Availability: N/A

Description

AI Translation Available

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

918

Server-Side Request Forgery (SSRF)

Incomplete
Abstraction: Base Structure: Simple
Common Consequences
Security Scopes Affected:
Confidentiality Integrity Access Control
Potential Impacts:
Read Application Data Execute Unauthorized Code Or Commands Bypass Protection Mechanism
Applicable Platforms
Technologies: Web Based, AI/ML, Web Server
View CWE Details
https://github.com/n8n-io/n8n/security/advisories/GHSA-c4f6…
https://github.com/n8n-io/n8n/security/advisories/GHSA-c4f6-59xq-95ww
https://www.vulncheck.com/advisories/n8n-before-ssrf-protec…
https://www.vulncheck.com/advisories/n8n-before-ssrf-protection-bypass-via-oaut…