n8n: Credential Authorization Bypass via Expression in HTTP Request Node `genericAuthType`
An authorization bypass vulnerability exists in n8n's HTTP Request node where an authenticated user with edit access to a shared workflow can reference another user's credential by specifying the credential type via an expression. This bypasses ownership checks due to improper pre-execution validation, allowing unauthorized use or exfiltration of credentials if the attacker knows the credential identifier. The issue affects versions prior to 1.123.67 and versions from 2.32.0 up to but not including 2.32.1. Fixed versions are 1.123.67, 2.31.5, and 2.32.1 or later. Temporary mitigations include restricting access to trusted users, excluding the HTTP Request node if not needed, and auditing credential sharing. No known exploits in the wild have been reported.
AI Analysis
Technical Summary
The vulnerability in n8n involves a credential authorization bypass in the HTTP Request node's genericAuthType parameter. An authenticated user with edit permissions on a shared workflow can exploit the fact that the pre-execution permission check validates the unresolved expression rather than the actual credential type. This flaw causes the ownership check to be skipped, enabling the user to load and use credentials they do not own at execution time. Exploitation requires knowledge of the target credential's identifier. The vulnerability is tracked as CWE-863 (Incorrect Authorization). It is fixed in n8n versions 1.123.67, 2.31.5, and 2.32.1. Users should upgrade to these versions or later to remediate the issue.
Potential Impact
An attacker with edit access to a shared workflow can bypass credential ownership checks and use or exfiltrate credentials belonging to other users if they know the credential identifier. This could lead to unauthorized access to sensitive systems or data that the credential protects. The vulnerability does not require UI interaction and has low attack complexity but requires some privileges (edit access) and knowledge of credential IDs. There are no known exploits in the wild at this time.
Mitigation Recommendations
A fix is available in n8n versions 1.123.67, 2.31.5, and 2.32.1 and later; users should upgrade to one of these versions to remediate the vulnerability. If immediate upgrade is not possible, administrators should restrict instance access to fully trusted users, exclude the HTTP Request node by adding 'n8n-nodes-base.httpRequest' to the NODES_EXCLUDE environment variable if the node is not required, and audit credential sharing and workflow access to limit exposure of credential identifiers. These workarounds do not fully remediate the risk and should be considered temporary.
n8n: Credential Authorization Bypass via Expression in HTTP Request Node `genericAuthType`
Description
An authorization bypass vulnerability exists in n8n's HTTP Request node where an authenticated user with edit access to a shared workflow can reference another user's credential by specifying the credential type via an expression. This bypasses ownership checks due to improper pre-execution validation, allowing unauthorized use or exfiltration of credentials if the attacker knows the credential identifier. The issue affects versions prior to 1.123.67 and versions from 2.32.0 up to but not including 2.32.1. Fixed versions are 1.123.67, 2.31.5, and 2.32.1 or later. Temporary mitigations include restricting access to trusted users, excluding the HTTP Request node if not needed, and auditing credential sharing. No known exploits in the wild have been reported.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in n8n involves a credential authorization bypass in the HTTP Request node's genericAuthType parameter. An authenticated user with edit permissions on a shared workflow can exploit the fact that the pre-execution permission check validates the unresolved expression rather than the actual credential type. This flaw causes the ownership check to be skipped, enabling the user to load and use credentials they do not own at execution time. Exploitation requires knowledge of the target credential's identifier. The vulnerability is tracked as CWE-863 (Incorrect Authorization). It is fixed in n8n versions 1.123.67, 2.31.5, and 2.32.1. Users should upgrade to these versions or later to remediate the issue.
Potential Impact
An attacker with edit access to a shared workflow can bypass credential ownership checks and use or exfiltrate credentials belonging to other users if they know the credential identifier. This could lead to unauthorized access to sensitive systems or data that the credential protects. The vulnerability does not require UI interaction and has low attack complexity but requires some privileges (edit access) and knowledge of credential IDs. There are no known exploits in the wild at this time.
Mitigation Recommendations
A fix is available in n8n versions 1.123.67, 2.31.5, and 2.32.1 and later; users should upgrade to one of these versions to remediate the vulnerability. If immediate upgrade is not possible, administrators should restrict instance access to fully trusted users, exclude the HTTP Request node by adding 'n8n-nodes-base.httpRequest' to the NODES_EXCLUDE environment variable if the node is not required, and audit credential sharing and workflow access to limit exposure of credential identifiers. These workarounds do not fully remediate the risk and should be considered temporary.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-6qc9-mqvw-jg7x
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a6150cc9c2644c7f8da0142
Added to database: 07/22/2026, 23:22:52 UTC
Last enriched: 07/22/2026, 23:27:16 UTC
Last updated: 07/22/2026, 23:27:16 UTC
Views: 2
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.