GHSA-6QC9-MQVW-JG7X

n8n: Credential Authorization Bypass via Expression in HTTP Request Node genericAuthType

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

• Restrict n8n instance access to fully trusted users only.
• Exclude the HTTP Request node by adding n8n-nodes-base.httpRequest to the NODES_EXCLUDE environment variable, if the node is not required.
• Audit credential sharing and workflow access to limit exposure of credential IDs to untrusted users.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

An authenticated member with edit access to a shared workflow could reference another user's credential in an HTTP Request node while specifying the credential type through an expression. Because the pre-execution permission check compared the unresolved expression instead of the real credential type, the ownership check was skipped and the credential was loaded at execution time, letting the member use or exfiltrate a credential they were never granted. Exploitation required knowing the target credential's identifier.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

Kodem intelligence

Already deployed Kodem?

The issue has been fixed in n8n versions 1.123.67, 2.31.5, and 2.32.1. Users should upgrade to one of these versions or later to remediate the vulnerability.

1. What is GHSA-6QC9-MQVW-JG7X? GHSA-6QC9-MQVW-JG7X is a high-severity incorrect authorization vulnerability in n8n (npm), affecting versions < 1.123.67. It is fixed in 1.123.67, 2.32.1, 2.31.5. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. Which versions of n8n are affected by GHSA-6QC9-MQVW-JG7X? n8n (npm) versions < 1.123.67 is affected.
3. Is there a fix for GHSA-6QC9-MQVW-JG7X? Yes. GHSA-6QC9-MQVW-JG7X is fixed in 1.123.67, 2.32.1, 2.31.5. Upgrade to this version or later.
4. Is GHSA-6QC9-MQVW-JG7X exploitable, and should I be worried? Whether GHSA-6QC9-MQVW-JG7X is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether GHSA-6QC9-MQVW-JG7X is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix GHSA-6QC9-MQVW-JG7X?
   • Upgrade n8n to 1.123.67 or later
   • Upgrade n8n to 2.32.1 or later
   • Upgrade n8n to 2.31.5 or later

Other vulnerabilities in n8n