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".
0.7%(unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 54th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-09-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-307Improper Restriction of Excessive Authentication Attempts CWE-799Improper Control of Interaction Frequency
Show the promptExplain CVE-2026-93650 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-93650?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-93650?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-93650 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Attack patterns (CAPEC)
CAPEC-16 Dictionary-based Password Attack Likelihood: Medium · Severity: High
CAPEC-49 Password Brute Forcing Likelihood: Medium · Severity: High
CAPEC-560 Use of Known Domain Credentials Likelihood: High · Severity: High
CAPEC-565 Password Spraying Likelihood: High · Severity: High
CAPEC-600 Credential Stuffing Likelihood: High · Severity: High
CAPEC-652 Use of Known Kerberos Credentials Likelihood: Medium · Severity: High
CAPEC-653 Use of Known Operating System Credentials Likelihood: High · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.