# CVE-2026-39851: Saleor has a user enumeration vulnerability due to different error messages

> Attackers can enumerate valid user email addresses via distinct error messages in the requestEmailChange mutation, exposing user data.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-m3rm-m4vq-27x7

## What is CVE-2026-39851?

CVE-2026-39851 is a medium-severity vulnerability in saleor, published on 8 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Saleor is an e-commerce platform. From 2.10.0 to before 3.23.0a3, 3.22.47, 3.21.54, and 3.20.118, the requestEmailChange() mutation was revealing the existence of user-provided email addresses in error messages. This vulnerability is fixed in 3.23.0a3, 3.22.47, 3.21.54, and 3.20.118.

Weakness: CWE-204 (Observable Response Discrepancy)

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

It affects 1 product.


Products: Saleor Saleor.

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

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

## Is CVE-2026-39851 being exploited?

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

## Other vulnerabilities in saleor

- [CVE-2026-24136](https://insights.sbomify.com/CVE-2026-24136/): Saleor has an Insecure Direct Object Reference (IDOR) in GraphQL API (high 8.7)
- [CVE-2026-23499](https://insights.sbomify.com/CVE-2026-23499/): Saleor vulnerable to stored XSS via Unrestricted File Upload (high 8.5)
- [CVE-2026-33756](https://insights.sbomify.com/CVE-2026-33756/): Saleor Affected by Denial of Service via Unbounded GraphQL Query Batching (high 7.5)
- [CVE-2026-35401](https://insights.sbomify.com/CVE-2026-35401/): Saleor has a resource exhaustion vulnerability in GraphQL queries (high 7.5)
- [CVE-2026-22849](https://insights.sbomify.com/CVE-2026-22849/): Saleor lacks proper HTML sanitization in rich text fields (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-39851 is a medium-severity vulnerability in saleor, published on 8 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-39851 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-39851/ (Markdown: https://insights.sbomify.com/CVE-2026-39851/index.md)
```

## Sources

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

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