Skip to content
Applications

CVE-2026-72772

8.9
High
EPSS 0.23%Patch availableAug 11, 2026

Authentication bypass in n8n embed login allows account takeover via unverified tokens

common questions

Is CVE-2026-72772 being exploited?

Not confirmed. CVE-2026-72772 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.23% probability of exploitation in the next 30 days.

How severe is CVE-2026-72772?

CVE-2026-72772 is rated High with a CVSS score of 8.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-72772?

Yes. A fix has been recorded for CVE-2026-72772. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-72772 affect?

CVE-2026-72772 affects n8n versions < 2.32.1 (and < 2.31.5), Instances with Embed Login enabled, Instances with a trusted key configured. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-72772?

Upgrade n8n to >=2.32.1 (or >=2.31.5), or disable Embed Login/remove untrusted keys until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
n8n versions < 2.32.1 (and < 2.31.5)Instances with Embed Login enabledInstances with a trusted key configured
impact

An attacker with a token accepted by a trusted key can authenticate as any user and gain full account control.

action required

Immediate action required

affected versions
n8n-io n8n
  • affected< 2.32.1
  • affected< 2.31.5
vendor says fixed in2.32.1, 2.31.5

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free