CVE-2026-77069n8n before 1.123.69 SSRF Protection Bypass via OAuth2
Updated under an hour ago ()
Does this affect you?
It affects n8n-io n8n and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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).
- CVSS
- 2.3 LOW (v4.0, CNA)CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N
- Weakness (CWE)
- CWE-918
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- VulnCheck
- NVD analysis
- Analyzed
- Record last updated
- Aug 21, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
n8n-io n8n n8n_io:n8n (from the name) | before 1.123.69; 1.123.69 not affected | CNA record |
n8n n8n n8n:n8n | before 1.123.69; from 2.33.0 before 2.33.4; 2.34.0 | NVD |
References
- https://github.com/n8n-io/n8n/security/advisories/GHSA-c4f6-59xq-95wwvendor-advisory, mitigation
- https://www.vulncheck.com/advisories/n8n-before-ssrf-protection-bypass-via-oauth2third-party-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.