CVE-2026-77069 json
n8n before 1.123.69 SSRF Protection Bypass via OAuth2
published 3mo ago modified 2mo ago also EUVD-2026-63258 , GHSA-c4f6-59xq-95ww
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository n8n-io/n8n. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 4.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 22%
- public exploits
- 0
- none known
Summary
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).
Patch / fix
- npm n8n >= 1.123.69, >= 2.33.4, >= 2.34.1
- n8n-io n8n 1.123.69, 2.33.4, 2.34.1
Is CVE-2026-77069 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 2.3 | 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 |
| CNA | 4.0 | 2.3 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | n8n | <1.123.69 <2.34.1 <2.33.4 |
>= 1.123.69 >= 2.34.1 >= 2.33.4 |
Affected products
- n8n-io n8n
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/n8n-io/n8n/security/advisories/GHSA-c4f6-59xq-95ww
vendor-advisory, mitigation, advisory
-
vulncheck.com
/advisories/n8n-before-ssrf-protection-bypass-via-oauth2
third-party-advisory
Sources
- CVE List CVE-2026-77069
- NVD CVE-2026-77069
- Maintainer advisory GHSA-c4f6-59xq-95ww
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of n8n-io/n8n published their own advisory on GitHub. Reviewed sources take precedence over it.