Summary
CVE-2026-63472 is a critical improper authentication vulnerability in Vendure, an open-source headless commerce platform, affecting the core ExternalAuthenticationService. Versions prior to 3.7.0 attach a newly presented external authentication method to an existing customer account based solely on a matching email address, without verifying that the email is actually owned by the person authenticating. This allows account takeover in deployments using custom external authentication strategies, and carries a CVSS v3.1 base score of 9.1 (Critical).
Technical details
- Root cause:
ExternalAuthenticationService.createCustomerAndUserlooks up an existing customer byemailAddressand links a new external authentication method to that account without requiring theverifiedflag on the identity to betrue. - Trigger conditions: The store must use a custom external
AuthenticationStrategythat can forward an email address whose ownership has not been verified by the external identity provider. - Attack vector: An attacker registers or authenticates with an external provider using a victim’s known email address, then authenticates to the Vendure store; the platform silently binds the attacker’s external identity to the victim’s existing account.
- Impact: The attacker gains full access to the victim’s account, including order history, saved addresses, and personal information, and can place orders or modify account data as the victim.
- Deployments using only native email/password authentication, or external strategies that strictly require provider-verified email ownership, are not affected.
Affected software
@vendure/core(Vendure) versions prior to 3.7.0
Severity
- CVSS v3.1 Base Score: 9.1 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Mitigation and recommended actions
- Immediate: Upgrade
@vendure/coreto version 3.7.0 or later, which requires a verified email before an external authentication method is linked to a pre-existing account. - If no patch can be applied immediately: Audit all custom external
AuthenticationStrategyimplementations to ensure they only setverified: truewhen the identity provider has actually confirmed ownership of the email address, and disable or restrict any external authentication strategies that cannot guarantee verified email ownership until the upgrade can be applied.

