# CVE-2026-63472: Vendure affected by external-authentication account takeover: external login linked to a pre-existing account by email without verification

> Attackers can take over victim accounts by linking unverified external identities to existing emails in custom authentication setups.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-6j36-r6pr-59x4

## What is CVE-2026-63472?

CVE-2026-63472 is a critical authentication bypass vulnerability in vendurehq vendure, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vendure is an open-source headless commerce platform. Prior to 3.7.0, ExternalAuthenticationService.createCustomerAndUser in packages/core/src/service/helpers/external-authentication/external-authentication.service.ts selects an existing customer user by emailAddress and attaches a newly presented ExternalAuthenticationMethod without requiring verified to be true. In deployments with a custom external AuthenticationStrategy that forwards an email whose ownership the provider has not verified, an attacker can authenticate with a victim's email and bind the attacker's external identity to the victim's existing account. This can expose orders, addresses, and personal information and permit account changes or orders as the victim. Native-only email and password deployments and external strategies that always require provider-verified email ownership are unaffected, and new-account creation for an unused email remains permitted. This issue is fixed in version 3.7.0.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-63472?

2 open source packages ship an affected version, including @vendure/core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@vendure/core` | npm | All versions | 3.7.0 |
| `@vendure/core` | npm | All versions | 3.7.0 |

## How do I fix CVE-2026-63472?

Upgrade @vendure/core to 3.7.0 or later.

## Is CVE-2026-63472 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63472 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63472 and fix it if it is affected.

What it is: CVE-2026-63472 is a critical authentication bypass vulnerability in vendurehq vendure, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63472 exists.

Affected packages and fixed versions:
- @vendure/core (npm): affected all versions; fixed in 3.7.0
- @vendure/core (npm): affected all versions; fixed in 3.7.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63472/ (Markdown: https://insights.sbomify.com/CVE-2026-63472/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63472
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63472
- OSV: https://osv.dev/vulnerability/CVE-2026-63472

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63472/
Summaries are generated and may contain mistakes; the official description above is the record.