CVE-2026-63472

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

const existingUser = await this.findExistingCustomerUserByEmailAddress(ctx, config.emailAddress);
if (existingUser) {
    user = existingUser;                 // <-- links to the EXISTING account, by email alone
} else {
    user = new User({ identifier: config.emailAddress, verified: config.verified || false, ... });
}
const authMethod = await this.connection.getRepository(ctx, ExternalAuthenticationMethod).save(
    new ExternalAuthenticationMethod({ externalIdentifier: config.externalIdentifier, strategy: config.strategy }),
);
user.authenticationMethods = [...(user.authenticationMethods || []), authMethod];   // <-- external login attached
await this.connection.getRepository(ctx, User).save(user);

Account takeover of any customer whose email address an attacker can present (unverified) via an external auth provider, read/modify the victim's orders, addresses, and PII, and place orders as them. The blast radius depends on the deployed AuthenticationStrategy(ies): strategies that don't strictly require a provider-verified email (or providers that don't guarantee email ownership) are directly exploitable.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2026-63472 has a CVSS score of 9.1 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.7.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Refuse to bind an external authentication method to a pre-existing account unless the email is provably verified, and prefer explicit, authenticated account-linking:

if (existingUser) {
    if (!config.verified) {
        // Do not silently link an unverified external identity to an existing account.
        throw new EmailAddressConflictError(); // or require the user to link while logged in
    }
    user = existingUser;
}

Document clearly that an AuthenticationStrategy MUST only set verified: true for provider-verified emails, and that linking to existing accounts requires it.

1. What is CVE-2026-63472? CVE-2026-63472 is a critical-severity improper authentication vulnerability in @vendure/core (npm), affecting versions < 3.7.0. It is fixed in 3.7.0. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is CVE-2026-63472? CVE-2026-63472 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @vendure/core are affected by CVE-2026-63472? @vendure/core (npm) versions < 3.7.0 is affected.
4. Is there a fix for CVE-2026-63472? Yes. CVE-2026-63472 is fixed in 3.7.0. Upgrade to this version or later.
5. Is CVE-2026-63472 exploitable, and should I be worried? Whether CVE-2026-63472 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
6. What actually determines whether CVE-2026-63472 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.
7. How do I fix CVE-2026-63472? Upgrade @vendure/core to 3.7.0 or later.