Authentication Bypass in @vendure/core (CVE-2026-63472)
Summary
Authentication bypass in @vendure/core (CVE-2026-63472). Confidential information can be exposed externally. Exploitable via AuthenticationStrategy. Mitigation: upgrade to 3.7.0 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-63472 has been found in @vendure/core.
Attackers can target a specific entry point like AuthenticationStrategy over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.1/10.
What to do: upgrade @vendure/core to 3.7.0 or later.
If unsure, ask your IT team or search "@vendure/core CVE-2026-63472" on the vendor's site.
CVE-2026-63472 (@vendure/core) — CWE-287 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: AuthenticationStrategy / emailAddress / ExternalAuthenticationService / email_verified
Patched: 3.7.0 — apply immediately
Workaround: set verified: true
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Authentication bypass (CWE-287) exists in @vendure/core. Attackers reach the vulnerable code path via AuthenticationStrategy without authentication.
Check the vendor advisory for the affected versions of @vendure/core. Attack surface: AuthenticationStrategy / emailAddress / ExternalAuthenticationService / email_verified.
Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally.
Update to 3.7.0.
Workaround: set verified: true
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@vendure/core' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@vendure/core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@vendure/coreを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
set verified: trueパッチが適用されるまでの応急処置として、set verified: true を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade @vendure/core to 3.7.0ステージング環境で 3.7.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- web github.com
- web github.com