{"answers":{"affected":"2 open source packages ship an affected version, including @vendure/core.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63472 exists.","fix":"Upgrade @vendure/core to 3.7.0 or later.","what":"CVE-2026-63472 is a critical authentication bypass vulnerability in vendurehq vendure, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-63472 and fix it if it is affected.\n\nWhat it is: CVE-2026-63472 is a critical authentication bypass vulnerability in vendurehq vendure, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63472 exists.\n\nAffected packages and fixed versions:\n- @vendure/core (npm): affected all versions; fixed in 3.7.0\n- @vendure/core (npm): affected all versions; fixed in 3.7.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-63472/ (Markdown: https://insights.sbomify.com/CVE-2026-63472/index.md)","id":"CVE-2026-63472","markdown":"https://insights.sbomify.com/CVE-2026-63472/index.md","name":"CVE-2026-63472","record":{"aliases":["GHSA-6j36-r6pr-59x4"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Vendure commerce platform","requires_auth":"none","summary":"Attackers can take over victim accounts by linking unverified external identities to existing emails in custom authentication setups.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Vendure affected by external-authentication account takeover: external login linked to a pre-existing account by email without verification","id":"CVE-2026-63472","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Hurl: Cookies in Cookies section leak when redirecting to a different host","id":"CVE-2026-63481"},"packages":[{"ecosystem":"npm","fixed":["3.7.0"],"introduced":["0"],"last_affected":[],"package":"@vendure/core","purl":null,"source":"GHSA-6j36-r6pr-59x4"},{"ecosystem":"npm","fixed":["3.7.0"],"introduced":["0"],"last_affected":[],"package":"@vendure/core","purl":"pkg:npm/%40vendure/core","source":"GHSA-6j36-r6pr-59x4"}],"prev":{"headline":"Unleash: Global Mustache.escape override disables HTML escaping process-wide, enabling Slack/Teams link-injection via unrestricted username","id":"CVE-2026-63466"},"products":["vendure"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-17","vendors":["vendurehq"]},"summary":"Attackers can take over victim accounts by linking unverified external identities to existing emails in custom authentication setups.","url":"https://insights.sbomify.com/CVE-2026-63472/"}