n8n before 1.123.69 SSRF Protection Bypass via OAuth2 (CVE-2026-77069) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-77069

n8n before 1.123.69 SSRF Protection Bypass via OAuth2

Answer in brief

CVE-2026-77069 records a Unknown severity vulnerability in n8n before 1.123.69 SSRF Protection Bypass via OAuth2. The current sources do not mark it as known exploited. The current feed maps n8n-io/n8n (generic), n8n-io/n8n (generic), n8n-io/n8n (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 20, 2026Updated Aug 20, 2026Source checked Aug 20, 2026First seen by HOL Aug 20, 2026Material review Aug 20, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 3 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps n8n-io/n8n (generic), n8n-io/n8n (generic), n8n-io/n8n (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
n8n-io/n8ngeneric	>=0 <1.123.69	1.123.69
n8n-io/n8ngeneric	>=0 <2.34.1	2.34.1
n8n-io/n8ngeneric	>=0 <2.33.4	2.33.4

Recommended response

Check inventory. Check lockfiles and deployed manifests for n8n-io/n8n, n8n-io/n8n, n8n-io/n8n.
Review the reported fix. Update n8n-io/n8n to 1.123.69; n8n-io/n8n to 2.34.1; n8n-io/n8n to 2.33.4 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 20, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 20, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 20, 2026

Sources and claim methodology

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

Quoted source text, attributed separately from HOL analysis.