n8n before 1.123.64, 2.29.8, and 2.30.1 fails to enforce the "Allowed HTTP Request Domains" restriction on HTTP-based credentials (Header Auth, Basic Auth, Query Auth, OAuth) in the GraphQL node, unlike the HTTP Request node. An authenticated user able to create or edit workflows can point the node's endpoint at a server they control and exfiltrate restricted credentials. Only instances where a credential has "Allowed HTTP Request Domains" configured and is usable by non-owner users are affected.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/n8n-io/n8n/security/advisories/GHSA-gq66-9cw5-j5jm Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.1 · n8nNVD modified 2026-10-24 17:10
Affected (CPE criteria) 4
cpe:2.3:a:n8n:n8n:*:*:*:*:community:node.js:*:*cpe:2.3:a:n8n:n8n:*:*:*:*:enterprise:node.js:*:*cpe:2.3:a:n8n:n8n:2.30.0:*:*:*:community:node.js:*:*cpe:2.3:a:n8n:n8n:2.30.0:*:*:*:enterprise:node.js:*:*
References 2
- https://github.com/n8n-io/n8n/security/advisories/GHSA-gq66-9cw5-j5jm Mitigation, Vendor Advisory
- https://www.vulncheck.com/advisories/n8n-before-credential-exfiltration-via-graphql-node Third Party Advisory