n8n before 1.123.69 Allowed-Domains Bypass via GraphQL Node (CVE-2026-77081) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-77081

n8n before 1.123.69 Allowed-Domains Bypass via GraphQL Node

Answer in brief

CVE-2026-77081 records a Unknown severity vulnerability in n8n before 1.123.69 Allowed-Domains Bypass via GraphQL Node. 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.x before 2.33.4, and 2.x before 2.34.1 contain an allowed-domains bypass in the GraphQL node. When the node's Authentication parameter is set to expression mode, every authentication-gated credential selector is treated as active; if two credentials of different types are attached, the node enforces the allowed-domains policy of only the first credential while still attaching material from both. An authenticated user with workflow-authoring rights can thereby send a domain-restricted credential to an attacker-controlled endpoint, exfiltrating it with the leaked credential's permissions.

Quoted source text, attributed separately from HOL analysis.