CVE-2026-65596: n8n before 1.123.64 Credential Exfiltration via GraphQL Node
Impact The GraphQL node did not enforce the "Allowed HTTP Request Domains" restriction on HTTP-based credentials (such as Header Auth, Basic Auth, Query Auth, and OAuth), unlike the HTTP Request node. An authenticated user able to create or edit workflows could therefore 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.
Patches The issue has been fixed in n8n versions 1.123.64, 2.29.8, and 2.30.1. Users should upgrade to one of these versions or later to remediate the vulnerability.
Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict workflow creation and editing permissions to fully trusted users only. - Restrict credential sharing to fully trusted users only. - Audit credentials with domain restrictions for unexpected sharing relationships.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Other sources
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.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.29.8 - Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.30.1 - Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 1.123.64 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 1.123.64 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.29.8 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.30.1 - Compensating control
Audit credentials with domain restrictions for unexpected sharing relationships.
- Compensating control
Restrict credential sharing to fully trusted users only.
- Compensating control
Restrict workflow creation and editing permissions to fully trusted users only.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-65596?
The severity of CVE-2026-65596 is medium with a CVSS score of 5.1.
How do I fix CVE-2026-65596?
To fix CVE-2026-65596, upgrade to n8n version 1.123.64 or later.
What are the potential impacts of CVE-2026-65596?
CVE-2026-65596 may result in credential exfiltration via the GraphQL node for users with edit permissions.
Who is affected by CVE-2026-65596?
n8n users prior to version 1.123.64 that utilize the GraphQL node are affected by CVE-2026-65596.
What type of vulnerability is CVE-2026-65596?
CVE-2026-65596 is a vulnerability related to credential exfiltration through the misuse of GraphQL nodes in n8n.