A vulnerability was determined in Saleor up to 3.20.118/3.21.54/3.22.47/3.23.14. This vulnerability affects the function get_client_ip of the file saleor/account/throttling.py. Executing a manipulation can lead to improper restriction of excessive authentication attempts. The attack can be executed remotely. The attack requires a high level of complexity. It is stated that the exploitability is difficult. The exploit has been publicly disclosed and may be utilized. The projects own issue #19203 internal ticket admits "IP can be spoofed in most deployments" and that its REAL_IP_ENVIRON-type setting bypasses get_client_ip; fix (right-to-left RFC 7239 hop selection) proposed but still unmerged. The vendor explains within an email, that "[t]his is not a vulnerability, this is working at intended, Saleor expects XFF to be configured properly".
CVE-2026-93650
This low-severity CVE scores 3.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.7
- EG Score
- 3.7(low)
- EG Risk
- 33(Track)EG Risk 33/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity37% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 18, 2026
Last Modified
September 18, 2026
References (7)
- cna@vuldbhttps://github.com/saleor/saleor/
- cna@vuldbhttps://github.com/saleor/saleor/issues/19203
- cna@vuldbhttps://github.com/zast-ai/vulnerability-reports/blob/main/saleor/bruteforce.md
- cna@vuldbhttps://vuldb.com/cve/CVE-2026-93650
- cna@vuldbhttps://vuldb.com/submit/933655
- cna@vuldbhttps://vuldb.com/vuln/407477
- cna@vuldbhttps://vuldb.com/vuln/407477/cti
Vendor Advisories for CVE-2026-93650(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 20:31 UTCEG score recompute
- 2026-09-18 20:27 UTCNVD updateCVSS v4 → 2.9
- 2026-09-18 19:54 UTCEG score recompute
- 2026-09-18 19:54 UTCMITRE cvelistV5CVSS v4 → 6.3
- 2026-09-18 19:27 UTCEG score recompute
- 2026-09-18 19:27 UTCNVD updateCVSS v4 → 2.9
- 2026-09-18 18:34 UTCEG score recompute
- 2026-09-18 18:34 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-93650?
When was CVE-2026-93650 disclosed?
What is the CVSS score of CVE-2026-93650?
How do I remediate CVE-2026-93650?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-93650
Is Your Infrastructure Affected by CVE-2026-93650?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.