Vulnerability in Saleor (CVE-2026-35401)
Summary
Vulnerability in Saleor (CVE-2026-35401). Risk of unauthorized operations or information disclosure. 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.0.0 to before 3.23.0a3, 3.22.47, 3.21.54, and 3.20.118, a malicious actor can include many GraphQL mutations or queries in a single API call using aliases or chaining multiple mutations, resulting in resource exhaustion. 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-35401 has been found in Saleor.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade Saleor to 3.23.0a3 or later.
If unsure, ask your IT team or search "Saleor CVE-2026-35401" on the vendor's site.
CVE-2026-35401 (Saleor) — CWE-770 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / 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-770) exists in Saleor.
Check the vendor advisory for the affected versions of Saleor.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
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