Skip to main content
VulnerabilityPublished

CVE-2026-93650: Saleor · CWE-307

Affects saleorSource GCVE Database

0
Compare
Authoritative record:CVE-2026-93650· Medium 6.3

Public exploit available · CVSS 6.3 Medium · fixed in 3.23.15 : patch saleor as a priority.

Data as of 2 Nov 2026, 22:58 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.23.15, 3.22.48, 3.21.55 +1
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 18 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CISA SSVC: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by VulDB

    , 5 hours before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. CISA SSVC assessment

    proof of concept public

    , 2 hours after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA SSVC, the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

What to do

Upgrade saleor/saleor to 3.23.15, 3.22.48, 3.21.55 or 3.20.119.

Affected software

ProductAffectedFixed in
GitHubsaleor/saleorpkg:github/saleor/saleorOther threatsAffected
  • <3.20.119
  • <3.21.55
  • <3.22.48
  • <3.23.15
Fixed in
  • 3.20.119
  • 3.21.55
  • 3.22.48
  • 3.23.15

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The vendor states this behavior is by design and expects proper configuration of the X-Forwarded-For header to prevent IP spoofing. Users should ensure their deployment correctly configures trusted proxy headers to mitigate this issue.

Description

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".

References

Community reviews

Loading reviews…