# CVE-2025-22151: Strawberry GraphQL has a type resolution vulnerability

> Attackers can access sensitive data or escalate privileges by exploiting type confusion in Strawberry GraphQL's relay node resolution.

- **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:** 9 Jan 2025
- **Updated:** 9 Jan 2025
- **Also known as:** GHSA-5xh2-23cc-5jc6, PYSEC-2026-1946

## What is CVE-2025-22151?

CVE-2025-22151 is a low-severity vulnerability in strawberry-graphql strawberry, published on 9 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Strawberry GraphQL is a library for creating GraphQL APIs. Starting in 0.182.0 and prior to version 0.257.0, a type confusion vulnerability exists in Strawberry GraphQL's relay integration that affects multiple ORM integrations (Django, SQLAlchemy, Pydantic). The vulnerability occurs when multiple GraphQL types are mapped to the same underlying model while using the relay node interface. When querying for a specific type using the global node field (e.g., FruitType:some-id), the resolver may incorrectly return an instance of a different type mapped to the same model (e.g., SpecialFruitType). This can lead to information disclosure if the alternate type exposes sensitive fields and potential privilege escalation if the alternate type contains data intended for restricted access. This vulnerability is fixed in 0.257.0.

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

## Which versions are affected by CVE-2025-22151?

3 open source packages ship an affected version, including strawberry-graphql.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `strawberry-graphql` | PyPI | From 0.182.0 | 0.257.0 |
| `strawberry-graphql` | PyPI | From 0.182.0 | 0.257.0 |
| `strawberry-graphql` | PyPI | From 0.182.0 | 0.257.0 |

## How do I fix CVE-2025-22151?

Upgrade strawberry-graphql to 0.257.0 or later.

## Is CVE-2025-22151 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-22151 and fix it if it is affected.

What it is: CVE-2025-22151 is a low-severity vulnerability in strawberry-graphql strawberry, published on 9 Jan 2025. 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-2025-22151 in the wild and no public exploit code.

Affected packages and fixed versions:
- strawberry-graphql (PyPI): affected from 0.182.0; fixed in 0.257.0
- strawberry-graphql (PyPI): affected from 0.182.0; fixed in 0.257.0
- strawberry-graphql (PyPI): affected from 0.182.0; fixed in 0.257.0

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

## Sources

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

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