GHSA-5xh2-23cc-5jc6 is a low-severity (CVSS 3.7) CWE-843 vulnerability in strawberry-graphql. A fix is available for strawberry-graphql — see the affected versions and patch details below.
Strawberry GraphQL has type resolution vulnerability in node interface that allows potential data leakage through incorrect type resolution
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-5xh2-23cc-5jc6.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-5xh2-23cc-5jc6 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
strawberry-graphqlReal-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
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | strawberry-graphql | ≥ 0.182.0&&< 0.257.0 | 0.257.0pip install --upgrade 'strawberry-graphql==0.257.0' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for strawberry-graphql, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update strawberry-graphql to 0.257.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5xh2-23cc-5jc6 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-5xh2-23cc-5jc6 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-5xh2-23cc-5jc6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-5xh2-23cc-5jc6 in your dependencies?
O3 Security finds GHSA-5xh2-23cc-5jc6 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.