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

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
• EPSS 0.6%, percentile 47: FIRST’s model estimates a 0.6% chance of exploitation activity in the next 30 days, higher than 47% of all scored CVEs (low). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Only applies if your dependency tree includes @vendure/core (npm) < 3.7.0, fixed in 3.7.0. Check your lockfile, including transitive dependencies.

What it is

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.

From the GitHub advisory

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

Package: @vendure/core (vendure-ecommerce/vendure, latest master) ·

> [!IMPORTANT] > This vulnerability only affects deployments that use external / social authentication (an AuthenticationStrategy other than the built-in native email/password strategy) where that strategy can return an email address the external provider has not verified the user owns.

You are affected if all of these are true: - Your store configures one or more external AuthenticationStrategy implementations (custom OAuth / social login / SSO), and - At least one forwards an emailAddress to ExternalAuthenticationService without guaranteeing the provider verified ownership of it (e.g. it doesn't check the provider's emailverified claim, or leaves verified unset/false), and - Customer accounts exist that share an email address with those external identities.

You are NOT affected if: - You use only the built-in native (email/password) authentication with no external strategies, or - Every external strategy you use only ever returns provider-verified emails (and sets verified: true).

Weakness type: CWE-287.

Product: @vendure/core (npm) · Assigned by: GitHub_M · Published: 2026-09-17

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: none (no login)
• User interaction: none
• Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation poc, automatable yes, technical impact total.
• FIRST EPSS (model of 2026-10-21): 0.59% probability of exploitation activity in the next 30 days; percentile 47.

Timeline

• 2026-09-17 — CVE record last updated
• 2026-09-17 — CVE record published by GitHub_M
• 2026-09-17 — GitHub-reviewed advisory GHSA-6j36-r6pr-59x4 published (critical)

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

1. GitHub Advisory GHSA-6j36-r6pr-59x4 github.com
2. CVE.org record CVE-2026-63472 cve.org
3. NVD entry CVE-2026-63472 nvd.nist.gov

Other references from the CVE record and advisory

1. github.com github.com
2. github.com github.com
3. github.com github.com

Critical npm advisories · Today’s Security Digest