What is GHSA-8342-988Q-86CR?

GHSA-8342-988Q-86CR 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.

Which versions of n8n are affected by GHSA-8342-988Q-86CR?

n8n (npm) versions >= 2.32.0, < 2.32.1 is affected.

Is there a fix for GHSA-8342-988Q-86CR?

Yes. GHSA-8342-988Q-86CR is fixed in 2.32.1, 2.31.5. Upgrade to this version or later.

Is GHSA-8342-988Q-86CR exploitable, and should I be worried?

Whether GHSA-8342-988Q-86CR 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.

What actually determines whether GHSA-8342-988Q-86CR 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.

How do I fix GHSA-8342-988Q-86CR?

Upgrade: n8n to 2.32.1 or later, n8n to 2.31.5 or later.

GHSA-8342-988Q-86CR in n8n

Q: Which versions of n8n are affected by GHSA-8342-988Q-86CR?

n8n (npm) versions >= 2.32.0, < 2.32.1 is affected.

Q: Is there a fix for GHSA-8342-988Q-86CR?

Yes. GHSA-8342-988Q-86CR is fixed in 2.32.1, 2.31.5. Upgrade to this version or later.

Q: Is GHSA-8342-988Q-86CR exploitable, and should I be worried?

Whether GHSA-8342-988Q-86CR 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.

Q: What actually determines whether GHSA-8342-988Q-86CR 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.

Q: How do I fix GHSA-8342-988Q-86CR?

Upgrade: n8n to 2.32.1 or later, n8n to 2.31.5 or later.

Summary

n8n: Account Takeover via Unverified Email Claim in Token Exchange Embed Login

Workarounds

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

Disable the embed login feature by setting N8N_TOKEN_EXCHANGE_ENABLED=false.
If embed login cannot be disabled, restrict network access to the n8n instance to fully trusted parties only, and audit all configured trusted keys and their allowedRoles assignments.
Review auth_identity records for unexpected token-exchange entries linked to high-privilege accounts.

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

Impact

In an n8n instance, when a validly-signed incoming token was matched to a local account by its email claim, the service did not check that the trusted key's permitted role ceiling covered that account, nor that the email claim was verified. As a result, anyone able to obtain a token accepted by one of the configured trusted keys, for example a trusted issuer that emitted unverified email addresses, could authenticate as any existing user, gaining full account control.

This issue only affects instances where the embed login feature is enabled and at least one trusted key source is configured.

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.

Affected versions

n8n (>= 2.32.0, < 2.32.1) n8n (< 2.31.5)

Security releases

n8n → 2.32.1 (npm) n8n → 2.31.5 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The issue has been fixed in n8n version 2.32.1. Users should upgrade to this version or later to remediate the vulnerability.

Frequently Asked Questions

What is GHSA-8342-988Q-86CR? GHSA-8342-988Q-86CR 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.
Which versions of n8n are affected by GHSA-8342-988Q-86CR? n8n (npm) versions >= 2.32.0, < 2.32.1 is affected.
Is there a fix for GHSA-8342-988Q-86CR? Yes. GHSA-8342-988Q-86CR is fixed in 2.32.1, 2.31.5. Upgrade to this version or later.
Is GHSA-8342-988Q-86CR exploitable, and should I be worried? Whether GHSA-8342-988Q-86CR 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
What actually determines whether GHSA-8342-988Q-86CR 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.
How do I fix GHSA-8342-988Q-86CR?
- Upgrade n8n to 2.32.1 or later
- Upgrade n8n to 2.31.5 or later

Other vulnerabilities in n8n

CVE-IDSeverityPackage summary

GHSA-652Q-GVQ3-74QVMediumn8n: n8n: Snowflake Node executeQuery Operation Allows SQL Injection via Unparameterized Expression Interpolation GHSA-JQWR-VX3P-R266Mediumn8n: n8n: PostgresTrigger Node SQL Injection Allows Authenticated Users to Execute Arbitrary SQL on Connected PostgreSQL Instances GHSA-9CMH-XCQM-5HQRMediumn8n: n8n: Cross-Tenant Module-Cache Poisoning in the JS Task Runner CVE-2026-65589Mediumn8n: n8n: Custom Header Credential Values Leaked in Plaintext into LLM Node Execution Data CVE-2026-65014Mediumn8n: n8n: Unauthenticated Endpoint Allows Cancellation of Any User's Active Test Webhook