# CVE-2026-44472: Saleor: Account pre-hijacking vulnerability due to unverified anonymous order merge

> 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.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-6whj-8p3f-2xqp

## What is CVE-2026-44472?

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.

### Official 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-44472?


## How do I fix CVE-2026-44472?

No fix has been published for CVE-2026-44472 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-44472 being exploited?

There is no known exploitation of CVE-2026-44472 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44472 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2026-44472 in the wild and no public exploit code.

Affected product: saleor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44472/ (Markdown: https://insights.sbomify.com/CVE-2026-44472/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44472
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44472
- OSV: https://osv.dev/vulnerability/CVE-2026-44472

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44472/
Summaries are generated and may contain mistakes; the official description above is the record.
