CVE-2026-65596 in n8n
Summary
by MITRE • 07/22/2026
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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 07/22/2026
The vulnerability in n8n versions prior to 1.123.64, 2.29.8, and 2.30.1 represents a critical authorization bypass affecting the GraphQL node's handling of HTTP-based credentials. This flaw stems from inconsistent enforcement of security controls between different node types within the platform's workflow execution engine. The root cause lies in the differential implementation of domain restriction policies where the HTTP Request node properly validates against allowed domains while the GraphQL node fails to apply these same restrictions to header authentication, basic authentication, query authentication, and OAuth credentials.
The technical exploitation occurs when authenticated users with workflow creation or editing privileges manipulate the GraphQL node configuration to target endpoints under their control. This allows for credential exfiltration from HTTP-based authentication mechanisms that should otherwise be restricted by domain policies. The vulnerability specifically impacts scenarios where credentials have "Allowed HTTP Request Domains" configured and are accessible to non-owner users, creating a privileged access vector that bypasses intended security boundaries. This represents a direct violation of the principle of least privilege and demonstrates a weakness in the platform's credential management architecture.
Operational impact of this vulnerability extends beyond simple data exfiltration to encompass potential lateral movement within affected environments. Attackers can leverage this flaw to harvest authentication tokens, API keys, and other sensitive credentials that are typically protected by domain restriction policies. The vulnerability affects organizations using n8n for workflow automation where credential sharing across user roles is permitted, creating a significant risk for enterprises with multi-tenant or shared environment configurations. This weakness undermines the security posture of automated workflows and could enable attackers to escalate privileges through credential theft.
Mitigation strategies should focus on immediate version upgrades to patched releases while implementing additional monitoring controls around credential usage patterns in GraphQL nodes. Organizations should review and tighten access controls for workflow editing capabilities, particularly for users who can modify credential configurations. The implementation of network segmentation and egress filtering can help limit potential exfiltration channels, though the most effective solution remains the application of vendor patches that ensure consistent enforcement of domain restrictions across all node types. This vulnerability aligns with CWE-284 Access Control Issues and maps to ATT&CK technique T1566 Credential Access through unauthorized workflow manipulation.
The flaw demonstrates a classic case of incomplete input validation and inconsistent security policy enforcement within a complex automation platform. Security teams should conduct comprehensive audits of their n8n deployments to identify affected instances and ensure all users with workflow editing privileges are properly vetted. Regular security assessments of credential handling mechanisms within automated workflows are essential to prevent similar issues in other components of the platform's architecture.