{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-44472 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-44472 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-44472 is a high-severity vulnerability in saleor, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-44472 and fix it if it is affected.\n\nWhat it is: CVE-2026-44472 is a high-severity vulnerability in saleor, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-44472 in the wild and no public exploit code.\n\nAffected product: saleor. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-44472/ (Markdown: https://insights.sbomify.com/CVE-2026-44472/index.md)","id":"CVE-2026-44472","markdown":"https://insights.sbomify.com/CVE-2026-44472/index.md","name":"CVE-2026-44472","record":{"aliases":["GHSA-6whj-8p3f-2xqp"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Saleor e-commerce platform","requires_auth":"none","summary":"Attackers can hijack accounts by registering with a victim's email, causing the system to merge anonymous order data into the attacker's account upon victim activation.","user_interaction":"required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Saleor is an e-commerce platform. From 2.10.0rc1 until 3.21.67, 3.22.63, and 3.23.22, the account activation flow treats email verification as sufficient proof of account ownership and automatically associates anonymous commerce data with the newly activated account. An attacker can use accountRegister to create an account with a victim's email address before the victim registers. If the victim follows the activation link sent to that mailbox, Saleor activates the attacker-created account and saleor/graphql/account/mutations/account/confirm_account.py can merge anonymous orders and gift-card data for the same email address without requiring the account password or another authentication factor. The attacker can then access the merged order history and personal data, including names, addresses, and phone numbers. The patched supported lines disable automatic merging by default, while the redesigned 3.24.0 flow requires password confirmation before anonymous objects are linked. This issue is fixed in versions 3.21.67, 3.22.63, and 3.23.22.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Saleor: Account pre-hijacking vulnerability due to unverified anonymous order merge","id":"CVE-2026-44472","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Ella Core: UE Downlink Redirection via Forged PDUSessionResourceSetupResponse","id":"CVE-2026-44473"},"packages":[],"prev":{"headline":"gitoxide: Symlink prefix-reuse allows worktree escape during checkout","id":"CVE-2026-44471"},"products":["saleor"],"published":"2026-08-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-18","vendors":["saleor"]},"summary":"Attackers can hijack accounts by registering with a victim's email, causing the system to merge anonymous order data into the attacker's account upon victim activation.","url":"https://insights.sbomify.com/CVE-2026-44472/"}