Quick answers
- Is CVE-2026-72772 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-72772 being exploited in the wild.
- How severe is CVE-2026-72772?
- High severity, with a CVSS score of 8.8, published 11 August 2026.
- Which products and versions are affected?
- N8n < 2.31.5, 2.32.0.
- Is there a fix for CVE-2026-72772?
- A patch was published on 2026-07-22: Fixed in versions 2.31.5 and 2.32.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-72772 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-72772?
- Check whether you run N8n at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This is an authentication bypass and privilege escalation vulnerability in n8n's embed login token exchange feature. The root cause is that when a validly-signed incoming token is matched to a local account by its email claim, the service fails to verify: (1) that the email claim itself is verified, and (2) that the trusted key's permitted role ceiling covers the target account. An attacker who obtains a token from any configured trusted key source—particularly those emitting unverified email addresses—can authenticate as any existing user. The attack requires network access to the n8n instance and valid signed token from a trusted issuer, but no prior authentication. The vulnerability is fixed in versions 2.31.5 and 2.32.1 or later.
Affected products
- n8n n8n < 2.31.5, 2.32.0
Identifiers
- CVE-2026-72772
- GHSA-8342-988q-86cr
Timeline
- 2026-07-22: disclosed
- 2026-07-22: patched: Fixed in versions 2.31.5 and 2.32.1