CVE-2025-22151: Strawberry GraphQL has type resolution vulnerability in node interface that allows potential data leakage through incorrect type resolution
Vulnerability Summary 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.
Published Jan 9, 2025
Affected packages
strawberry-graphql
- Ecosystem
- PyPI
- Affected
- >= 0.182.0, < 0.257.0
- Fixed in
- 0.257.0
- Check
pip show strawberry-graphql
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Vulnerability Summary 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.
Affected Components
- Strawberry GraphQL relay integration
- Specifically impacts implementations using:
- Django integration
- SQLAlchemy integration
- Pydantic integration
Technical Details
The vulnerability manifests when:
- Multiple GraphQL types inherit from
relay.Node - These types are mapped to the same database model
- The global
nodefield is used for type resolution
Example of vulnerable code:
from fruits.models import Fruit
import strawberry_django
import strawberry
@strawberry_django.type(Fruit)
class FruitType(relay.Node):
name: strawberry.auto
@strawberry_django.type(Fruit)
class SpecialFruitType(relay.Node):
secret_name: strawberry.auto
@strawberry.type
class Query:
node: relay.Node = strawberry_django.node()Security Impact
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
- Potential privilege escalation if the alternate type contains data intended for restricted access
Note Even with knowledge of the correct type name (e.g., SpecialFruitType), attackers may still be able to access unauthorized data through direct type queries.
We recommend to use permission on fields instead of creating a dedicate type.
Recommendations
- Avoid mapping multiple relay Node types to the same model
- Implement strict access controls at the field resolution level (using permissions)
- Consider using separate models for different access levels of the same data
- Update to
strawberry-graphql>=0.257.0 - If using
strawberry-graphql-django, update tostrawberry-graphql-django>=0.54.0
Credited to jamietdavidson, bellini666, patrick91.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-107727
Strawberry legacy graphql-ws retains naturally completed subscription slots
low3.7Oct 9, 2026CVE-2026-107728
Strawberry GraphQL: Synchronous permission checks can treat an awaitable authorization result as truthy
high7.5Oct 9, 2026CVE-2026-47706
Strawberry GraphQL has a Circular Fragment Reference DOS
medium5.3Jun 4, 2026CVE-2026-47707
Strawberry GraphQL's Bypass of MaxAliasesLimiter via Fragment Spreads leading to GraphQL Alias Amplification
medium5.3Jun 4, 2026CVE-2026-45739
Strawberry GraphQL: Default GraphiQL may expose HTTP headers in URLs
low3.1May 19, 2026CVE-2026-35523
strawberry-graphql: Authentication bypass via legacy graphql-ws WebSocket subprotocol
high7.5Apr 6, 2026
