CVE-2026-65596: Incorrect Authorization in n8n-io n8n
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.
AI Analysis
Technical Summary
CVE-2026-65596 is an incorrect authorization vulnerability in n8n's GraphQL node affecting versions prior to 1.123.64, from 1.123.64 up to but not including 2.29.8, and from 2.29.8 up to but not including 2.30.1. The vulnerability arises because the GraphQL node does not enforce the "Allowed HTTP Request Domains" restriction on HTTP-based credentials (Header Auth, Basic Auth, Query Auth, OAuth), unlike the HTTP Request node. This allows an authenticated user with workflow creation or editing privileges to configure the node to send requests to attacker-controlled servers, potentially exfiltrating credentials that should be restricted by domain. The issue only impacts credentials that have domain restrictions configured and are usable by users other than the credential owner.
Potential Impact
An authenticated user with permission to create or edit workflows can bypass domain restrictions on HTTP-based credentials in the GraphQL node, potentially exfiltrating sensitive credential data to attacker-controlled endpoints. This undermines the intended security controls on credential usage within n8n instances. The impact is limited to instances where domain restrictions are configured on credentials and those credentials are accessible by non-owner users. There are no known exploits in the wild as of the published date.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict workflow creation and editing permissions to trusted users only, and review credential configurations to limit usage by non-owner users. Monitor vendor communications for official patches or updates addressing this issue.
CVE-2026-65596: Incorrect Authorization in n8n-io n8n
Description
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.
CVSS v4.0
Score 5.1medium
Affected software
pkg:github/n8n-io/n8nRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-65596 is an incorrect authorization vulnerability in n8n's GraphQL node affecting versions prior to 1.123.64, from 1.123.64 up to but not including 2.29.8, and from 2.29.8 up to but not including 2.30.1. The vulnerability arises because the GraphQL node does not enforce the "Allowed HTTP Request Domains" restriction on HTTP-based credentials (Header Auth, Basic Auth, Query Auth, OAuth), unlike the HTTP Request node. This allows an authenticated user with workflow creation or editing privileges to configure the node to send requests to attacker-controlled servers, potentially exfiltrating credentials that should be restricted by domain. The issue only impacts credentials that have domain restrictions configured and are usable by users other than the credential owner.
Potential Impact
An authenticated user with permission to create or edit workflows can bypass domain restrictions on HTTP-based credentials in the GraphQL node, potentially exfiltrating sensitive credential data to attacker-controlled endpoints. This undermines the intended security controls on credential usage within n8n instances. The impact is limited to instances where domain restrictions are configured on credentials and those credentials are accessible by non-owner users. There are no known exploits in the wild as of the published date.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict workflow creation and editing permissions to trusted users only, and review credential configurations to limit usage by non-owner users. Monitor vendor communications for official patches or updates addressing this issue.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-22T10:45:44.833Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a60ab939c2644c7f8eced45
Added to database: 07/22/2026, 11:37:55 UTC
Last enriched: 07/22/2026, 11:53:21 UTC
Last updated: 07/23/2026, 02:51:54 UTC
Views: 16
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.