CVE-2023-26052 — saleor
LOWCVE-2023-26052 is a low-severity (CVSS 3.7) CWE-209 vulnerability in saleor. A fix is available for saleor — see the affected versions and patch details below.
Saleor is vulnerable to unauthenticated information disclosure via Python exceptions
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-26052.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2023-26052 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
saleor🐍saleor🐍saleor🐍saleor🐍saleor🐍saleorReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Saleor is a headless, GraphQL commerce platform delivering personalized shopping experiences. Some internal Python exceptions are not handled properly and thus are returned in API as error messages. Some messages might contain sensitive information like infrastructure details in unauthenticated requests. This issue has been patched in versions 3.1.48, 3.7.59, 3.8.0, 3.9.27, 3.10.14 and 3.11.12.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | saleor | ≥ 2.0.0&&< 3.1.48 | 3.1.48pip install --upgrade 'saleor==3.1.48' |
| 🐍PyPI | saleor | ≥ 3.11.0&&< 3.11.12 | 3.11.12pip install --upgrade 'saleor==3.11.12' |
| 🐍PyPI | saleor | ≥ 3.10.0&&< 3.10.14 | 3.10.14pip install --upgrade 'saleor==3.10.14' |
| 🐍PyPI | saleor | ≥ 3.9.0&&< 3.9.27 | 3.9.27pip install --upgrade 'saleor==3.9.27' |
| 🐍PyPI | saleor | ≥ 3.8.0&&< 3.8.30 | 3.8.30pip install --upgrade 'saleor==3.8.30' |
| 🐍PyPI | saleor | ≥ 3.7.0&&< 3.7.59 | 3.7.59pip install --upgrade 'saleor==3.7.59' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for saleor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update saleor to 3.1.48 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-26052 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2023-26052 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2023-26052. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2023-26052 in your dependencies?
O3 Security finds CVE-2023-26052 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.