GHSA-64XH-79J6-R5V8

n8n: Bypass "Allowed HTTP Request Domains" Credential Restriction in Multiple AI and LLM Nodes

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.

The credential "Allowed HTTP Request Domains" allowlist was intended to restrict which hosts a credential's secret could be sent to, protecting shared credentials from users who could use but not view them. Several AI/LLM nodes did not enforce this allowlist when a user-supplied base or endpoint URL was set. A low-privileged workflow editor with use-only access to such a shared credential could point one of these nodes at an attacker-controlled host and cause the credential secret to be transmitted there, then reuse it against the underlying service.

Only instances where a credential has "Allowed HTTP Request Domains" configured and is shared with non-owner users are affected.

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 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-64XH-79J6-R5V8? GHSA-64XH-79J6-R5V8 is a high-severity incorrect authorization vulnerability in n8n (npm), affecting versions >= 2.32.0, < 2.32.1. It is fixed in 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-64XH-79J6-R5V8? n8n (npm) versions >= 2.32.0, < 2.32.1 is affected.
3. Is there a fix for GHSA-64XH-79J6-R5V8? Yes. GHSA-64XH-79J6-R5V8 is fixed in 2.32.1, 2.31.5. Upgrade to this version or later.
4. Is GHSA-64XH-79J6-R5V8 exploitable, and should I be worried? Whether GHSA-64XH-79J6-R5V8 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-64XH-79J6-R5V8 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-64XH-79J6-R5V8?
   • Upgrade n8n to 2.32.1 or later
   • Upgrade n8n to 2.31.5 or later

Other vulnerabilities in n8n