Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-63472 – Authentication Bypass / Account Takeover – Vendure < 3.7.0

Be the first to know when new zero-days emerge:

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.createCustomerAndUser looks up an existing customer by emailAddress and links a new external authentication method to that account without requiring the verified flag on the identity to be true.
  • Trigger conditions: The store must use a custom external AuthenticationStrategy that 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/core to 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 AuthenticationStrategy implementations to ensure they only set verified: true when 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.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge