GHSA-364X-8G5J-X2PR

Workarounds

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

• Limit credential creation and sharing permissions to fully trusted users only.
• Restrict access to the n8n instance to trusted users only.

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

An authenticated user with permission to create and share credentials could craft a malicious OAuth2 credential containing a JavaScript URL in the Authorization URL field. If a victim opened the credential and interacted with the OAuth authorization button, the injected script would execute in their browser session.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

GHSA-364X-8G5J-X2PR has a CVSS score of 5.4 (Medium). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.8.0, 2.6.4); upgrading removes the vulnerable code path.

Kodem intelligence

The issue has been fixed in n8n versions 2.8.0 and 2.6.4. Users should upgrade to one of these versions or later to remediate the vulnerability.

1. What is GHSA-364X-8G5J-X2PR? GHSA-364X-8G5J-X2PR is a medium-severity cross-site scripting (XSS) vulnerability in n8n (npm), affecting versions >= 2.7.0, < 2.8.0. It is fixed in 2.8.0, 2.6.4. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is GHSA-364X-8G5J-X2PR? GHSA-364X-8G5J-X2PR has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of n8n are affected by GHSA-364X-8G5J-X2PR? n8n (npm) versions >= 2.7.0, < 2.8.0 is affected.
4. Is there a fix for GHSA-364X-8G5J-X2PR? Yes. GHSA-364X-8G5J-X2PR is fixed in 2.8.0, 2.6.4. Upgrade to this version or later.
5. Is GHSA-364X-8G5J-X2PR exploitable, and should I be worried? Whether GHSA-364X-8G5J-X2PR 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
6. What actually determines whether GHSA-364X-8G5J-X2PR 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.
7. How do I fix GHSA-364X-8G5J-X2PR?
   • Upgrade n8n to 2.8.0 or later
   • Upgrade n8n to 2.6.4 or later