Vulnerability in Saleor (CVE-2026-35407)
Summary
Vulnerability in Saleor (CVE-2026-35407). Data can be tampered with by attackers. Mitigation: upgrade to 3.23.0a3 or later.
Original description
The description as published by the source.
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 account’s email address is then updated to the token's new_email, even though that token was never issued for that account. This vulnerability is fixed in 3.23.0a3, 3.22.47, 3.21.54, and 3.20.118.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-35407 has been found in Saleor.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade Saleor to 3.23.0a3 or later.
If unsure, ask your IT team or search "Saleor CVE-2026-35407" on the vendor's site.
CVE-2026-35407 (Saleor) — CWE-285 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 3.23.0a3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-285) exists in Saleor.
Check the vendor advisory for the affected versions of Saleor.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to 3.23.0a3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Saleor' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Saleor' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Saleorを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Saleor to 3.23.0a3ステージング環境で 3.23.0a3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com
- patch github.com
- patch github.com
- patch github.com