# CVE-2023-26052: Saleor is vulnerable to unauthenticated information disclosure via Python exceptions > Unauthenticated attackers can obtain sensitive infrastructure details via unhandled Python exceptions in the Saleor GraphQL API. - **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 2 Mar 2023 - **Updated:** 5 Mar 2025 - **Also known as:** GHSA-3hvj-3cg9-v242, PYSEC-2026-915 ## What is CVE-2023-26052? CVE-2023-26052 is a low-severity vulnerability in saleor, published on 2 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information) ## Which versions are affected by CVE-2023-26052? 13 open source packages ship an affected version, including saleor. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `saleor` | PyPI | From 2.0.0 | 3.1.48, 3.7.59, 3.8.30, 3.9.27, 3.10.14, 3.11.12 | | `saleor` | PyPI | From 2.0.0 | 3.1.48 | | `saleor` | PyPI | From 2.0.0 | 3.1.48 | | `saleor` | PyPI | From 3.10.0 | 3.10.14 | | `saleor` | PyPI | From 3.10.0 | 3.10.14 | | `saleor` | PyPI | From 3.11.0 | 3.11.12 | | `saleor` | PyPI | From 3.11.0 | 3.11.12 | | `saleor` | PyPI | From 3.7.0 | 3.7.59 | | `saleor` | PyPI | From 3.7.0 | 3.7.59 | | `saleor` | PyPI | From 3.8.0 | 3.8.30 | | `saleor` | PyPI | From 3.8.0 | 3.8.30 | | `saleor` | PyPI | From 3.9.0 | 3.9.27 | | `saleor` | PyPI | From 3.9.0 | 3.9.27 | Products: Saleor Saleor. ## How do I fix CVE-2023-26052? Upgrade saleor to a fixed version for your release line: 3.1.48, 3.7.59, 3.8.30 or 3.9.27. ## Is CVE-2023-26052 being exploited? There is no known exploitation of CVE-2023-26052 in the wild and no public exploit code. ## Other vulnerabilities in saleor - [CVE-2026-24136](https://insights.sbomify.com/CVE-2026-24136/): Saleor has an Insecure Direct Object Reference (IDOR) in GraphQL API (high 8.7) - [CVE-2026-23499](https://insights.sbomify.com/CVE-2026-23499/): Saleor vulnerable to stored XSS via Unrestricted File Upload (high 8.5) - [CVE-2026-33756](https://insights.sbomify.com/CVE-2026-33756/): Saleor Affected by Denial of Service via Unbounded GraphQL Query Batching (high 7.5) - [CVE-2026-35401](https://insights.sbomify.com/CVE-2026-35401/): Saleor has a resource exhaustion vulnerability in GraphQL queries (high 7.5) - [CVE-2026-22849](https://insights.sbomify.com/CVE-2026-22849/): Saleor lacks proper HTML sanitization in rich text fields (high 7.2) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-26052 and fix it if it is affected. What it is: CVE-2023-26052 is a low-severity vulnerability in saleor, published on 2 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-26052 in the wild and no public exploit code. Affected packages and fixed versions: - saleor (PyPI): affected from 2.0.0; fixed in 3.1.48, 3.7.59, 3.8.30, 3.9.27, 3.10.14, 3.11.12 - saleor (PyPI): affected from 2.0.0; fixed in 3.1.48 - saleor (PyPI): affected from 2.0.0; fixed in 3.1.48 - saleor (PyPI): affected from 3.10.0; fixed in 3.10.14 - saleor (PyPI): affected from 3.10.0; fixed in 3.10.14 - saleor (PyPI): affected from 3.11.0; fixed in 3.11.12 - saleor (PyPI): affected from 3.11.0; fixed in 3.11.12 - saleor (PyPI): affected from 3.7.0; fixed in 3.7.59 - saleor (PyPI): affected from 3.7.0; fixed in 3.7.59 - saleor (PyPI): affected from 3.8.0; fixed in 3.8.30 - saleor (PyPI): affected from 3.8.0; fixed in 3.8.30 - saleor (PyPI): affected from 3.9.0; fixed in 3.9.27 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-26052/ (Markdown: https://insights.sbomify.com/CVE-2023-26052/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-26052 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-26052 - OSV: https://osv.dev/vulnerability/CVE-2023-26052 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-26052/ Summaries are generated and may contain mistakes; the official description above is the record.