Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-35407: Saleor is an e-commerce platform

28
Routine
MEDIUM 6.5UPGRADE

CVE-2026-35407 is a medium-severity flaw (CVSS 6.5) affecting saleor. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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, a business-logic and authorization flaw was found in the account email change workflow, the confirmation flow did not verify that the email change confirmation token was issued for the given authenticated user. As a result, a valid email-change token generated for one account can be replayed while authenticated as a different account. The second acco

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score6.5 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.3% (top 78%)
CISA exploited listNo
WeaknessCWE-285
Published2026-04-08
Last modified2026-07-24
Publisher (CNA): GitHub, Inc. · Vendor: saleor

Share: LinkedIn · X · Reddit

Last updated 2026-07-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

saleor saleor UPGRADE
Affected: >= 2.10.0 and < 3.20.118 · >= 3.20.119 and < 3.21.54 · >= 3.22.0 and < 3.22.47 · 3.23.0 · 3.23.0 a0 · 3.23.0 a1 · 3.23.0 a2
Fixed in: 3.20.118, 3.21.54, 3.22.47
Safe to downgrade to: a release before 2.10.0
1. Check installed version
apt-cache policy saleor || rpm -q saleor || saleor --version
2. UPGRADE to 3.20.118 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade saleor
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade saleor
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 2.10.0 (Debian / Ubuntu)
apt-cache madison saleor sudo apt install saleor=<VERSION_BEFORE_2.10.0> sudo apt-mark hold saleor
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list saleor sudo dnf downgrade saleor-<VERSION_BEFORE_2.10.0> sudo dnf versionlock add saleor
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-35407?

saleor: upgrade to 3.20.118, 3.21.54, 3.22.47. Exact commands for each OS are on this page.

Is CVE-2026-35407 being exploited?

CVE-2026-35407 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-35407 affect?

CVE-2026-35407 affects saleor. Severity is medium (CVSS 6.5). 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, a business-logic and authorization flaw was found in the account email change workflow, the confirmation flow did not verify that the email ch

How urgent is CVE-2026-35407?

Priority 28/100. No elevated risk signals yet.

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.