# CVE-2026-24136: Saleor has an Insecure Direct Object Reference (IDOR) in GraphQL API

> Unauthenticated attackers can extract sensitive PII from orders via an IDOR vulnerability in the GraphQL API.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jan 2026
- **Updated:** 26 Jan 2026
- **Also known as:** GHSA-r6fj-f4r9-36gr

## What is CVE-2026-24136?

CVE-2026-24136 is a high-severity vulnerability in saleor, published on 23 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Saleor is an e-commerce platform. Versions 3.2.0 through 3.20.109, 3.21.0-a.0 through 3.21.44 and 3.22.0-a.0 through 3.22.28 have a n Insecure Direct Object Reference (IDOR) vulnerability that allows unauthenticated actors to extract sensitive information in plain text. Orders created before Saleor 3.2.0 could have PIIs exfiltrated. The issue has been patched in Saleor versions: 3.22.29, 3.21.45, and 3.20.110. To workaround, temporarily block non-staff users from fetching order information (the order() GraphQL query) using a WAF.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-24136?

It affects 1 product.


Products: Saleor Saleor.

## How do I fix CVE-2026-24136?

No fix has been published for CVE-2026-24136 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-24136 being exploited?

There is no known exploitation of CVE-2026-24136 in the wild and no public exploit code.

Public exploit code:

- CVE-2026-24136 | Lab khai thác lỗ hổng IDOR trên Saleor GraphQL - query order() không kiểm tra xác thực, lộ toàn bộ PII (email, địa chỉ, SĐT) của khách hàng. Bao gồm môi trường Docker, script seed data và PoC. CVSS 4.0: 8.7 HIGH. (github_poc): https://github.com/BlankBire/CVE-2026-24136-Lab

## Other vulnerabilities in saleor

- [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)
- [CVE-2023-26051](https://insights.sbomify.com/CVE-2023-26051/): Saleor is vulnerable to staff-authenticated error message information disclosure vulnerability via Python exceptions (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24136 and fix it if it is affected.

What it is: CVE-2026-24136 is a high-severity vulnerability in saleor, published on 23 Jan 2026. 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-2026-24136 in the wild and no public exploit code.

Affected product: saleor. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2026-24136/ (Markdown: https://insights.sbomify.com/CVE-2026-24136/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24136
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24136
- OSV: https://osv.dev/vulnerability/CVE-2026-24136

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24136/
Summaries are generated and may contain mistakes; the official description above is the record.