GHSA-8342-988q-86cr: n8n Account Takeover Vulnerability

HIGH
CWE-345 CWE-863
Published
Advisory Summary

GHSA-8342-988q-86cr is a HIGH account takeover vulnerability (CWE-345: Insufficient Verification of Data Authenticity) affecting n8n libraries in the npm ecosystem. The issue involves account takeover via unverified email claim in token exchange embed login. Remediation is available by upgrading affected packages to version 2.32.1, 2.31.5.

GHSA-8342-988q-86cr at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-8342-988q-86cr
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-345: Insufficient Verification of Data Authenticity
Affected Product n8n
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-8342-988q-86cr

To remediate this vulnerability, upgrade all affected n8n dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

n8n fixed: 2.32.1
npm install n8n@2.32.1
n8n fixed: 2.31.5
npm install n8n@2.31.5
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls n8n

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-8342-988q-86cr, inspect your project dependencies using npm:

npm ls n8n

Analyze the terminal output to locate any version of n8n in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.32.1), your application is affected.

Note: The npm ls n8n command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-345: Insufficient Verification of Data Authenticity, where the product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. In n8n, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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. ## Patches The issue has been fixed in n8n version 2.32.1. Users should upgrade to this version or later to remediate the vulnerability. ## 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.

GHSA-8342-988q-86cr Affected n8n Versions

2 component(s)
Fixed Versions:
2.32.12.31.5
Product / Package Ecosystem Affected Versions Fixed Version
n8n
npm
≥ 2.32.0
< 2.32.1
2.32.1
n8n
npm
< 2.31.5
2.31.5

References

Frequently Asked Questions

What is GHSA-8342-988q-86cr?
GHSA-8342-988q-86cr is a security vulnerability in n8n involving Account Takeover via Unverified Email Claim in Token Exchange Embed Login under CWE-345: Insufficient Verification of Data Authenticity.
Which n8n versions are affected?
Affected versions include releases prior to 2.32.1, 2.31.5 across affected packages: n8n.
What version fixes GHSA-8342-988q-86cr?
Upgrading to 2.32.1, 2.31.5 (or the latest patched release for your respective branch) resolves the vulnerability.
Is n8n affected?
Yes, n8n is affected in releases prior to 2.32.1, 2.31.5. Upgrade your dependency to 2.32.1, 2.31.5 or later.
What CWE is associated with GHSA-8342-988q-86cr?
GHSA-8342-988q-86cr is classified under CWE-345: Insufficient Verification of Data Authenticity (The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.).
How can I check npm dependencies for GHSA-8342-988q-86cr?
Run the dependency tree command: 'npm ls n8n'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-8342-988q-86cr",
  "modified" : "2026-07-22T22:04:55Z",
  "published" : "2026-07-22T22:04:54Z",
  "aliases" : [ ],
  "summary" : "n8n: Account Takeover via Unverified Email Claim in Token Exchange Embed Login",
  "details" : "## Impact\n\nIn 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.\n\nThis issue only affects instances where the embed login feature is enabled and at least one trusted key source is configured.\n\n## Patches\n\nThe issue has been fixed in n8n version 2.32.1. Users should upgrade to this version or later to remediate the vulnerability.\n\n## Workarounds\n\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Disable the embed login feature by setting `N8N_TOKEN_EXCHANGE_ENABLED=false`.\n- 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.\n- Review `auth_identity` records for unexpected `token-exchange` entries linked to high-privilege accounts.\n\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.32.0"
      }, {
        "fixed" : "2.32.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.31.5"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/security/advisories/GHSA-8342-988q-86cr"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/commit/f69dfc6dd2178a14ea1624d2e1d403c2e755042f"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/n8n-io/n8n"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@2.31.5"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@2.32.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-345", "CWE-863" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-22T22:04:54Z",
    "nvd_published_at" : null
  }
}