CVE-2023-26051 is a medium-severity (CVSS 6.5) CWE-209 vulnerability in saleor. O3 Security confirms whether CVE-2023-26051 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Saleor is vulnerable to staff-authenticated error message information disclosure vulnerability via Python exceptions
Real-World Exposure
saleor🐍saleor🐍saleor🐍saleor🐍saleor🐍saleor🐍saleor🐍saleor+4 moreReal-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 user email address in staff-authenticated requests.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | saleor | ≥ 2.0.0&&< 3.1.48 | 3.1.48 |
| 🐍PyPI | saleor | ≥ 3.11.0&&< 3.11.12 | 3.11.12 |
| 🐍PyPI | saleor | ≥ 3.10.0&&< 3.10.14 | 3.10.14 |
| 🐍PyPI | saleor | ≥ 3.9.0&&< 3.9.27 | 3.9.27 |
| 🐍PyPI | saleor | ≥ 3.8.0&&< 3.8.30 | 3.8.30 |
| 🐍PyPI | saleor | ≥ 3.7.0&&< 3.7.59 | 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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-26051 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 pinpoints whether CVE-2023-26051 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2023-26051. 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-26051 in your dependencies?
O3 detects CVE-2023-26051 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.