Strawberry GraphqlApplication · Strawberry
CVE-2026-35526
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedStrawberry GraphQL is a library for creating GraphQL APIs. Prior to 0.312.3, Strawberry GraphQL's WebSocket subscription handlers for both the graphql-transport-ws and legacy graphql-ws protocols allocate an asyncio.Task and associated Operation object for every incoming subscribe message without enforcing any limit on the number of active subscriptions per connection. An unauthenticated attacker can open a single WebSocket connection, send connection_init, and then flood subscribe messages with unique IDs. Each message unconditionally spawns a new asyncio.Task and async generator, causing linear memory growth and event loop saturation. This leads to server degradation or an OOM crash. This vulnerability is fixed in 0.312.3.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceStrawberry GraphQL's WebSocket subscription handlers for graphql-transport-ws and legacy graphql-ws protocols lack per-connection subscription limits. Each incoming subscribe message with a unique ID unconditionally spawns a new asyncio.Task and async generator, enabling an unauthenticated attacker with a single WebSocket connection to flood subscribe messages, causing linear memory growth, event loop saturation, and eventual server degradation or OOM crash.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Strawberry GraphqlApplication
< 0.312.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Strawberry GraphQL versionRun 'pip show strawberry-graphql' or check your poetry/pyproject.lock for the strawberry-graphql versionAffected if The version is lower than 0.312.3
-
Verify WebSocket subscription handler is in useInspect your Strawberry GraphQL server configuration for Subscription type definitions and ensure subscriptions are exposed via WebSocket (check for GraphQLSubscriptionTransport or similar WebSocket transport setup in your app)Affected if WebSocket subscriptions are enabled and active in your deployment
-
Confirm subscription endpoint is exposedCheck if your GraphQL endpoint exposes a /ws or websocket subscription path (such as /graphql/ws) that accepts WebSocket connections for subscriptionsAffected if A WebSocket subscription endpoint is publicly accessible without additional rate limiting controls
Your environment is affected if you are running Strawberry GraphQL version lower than 0.312.3 AND you have WebSocket subscriptions enabled with an exposed subscription endpoint that lacks connection-level rate limiting.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.312.3
Upgrade to Strawberry GraphQL 0.312.3 or later. Additionally, implement connection-level subscription rate limiting as defense-in-depth to prevent resource exhaustion even if the library version cannot be immediately updated.
0.312.3
- Check current installed version of strawberry-graphql using: pip show strawberry-graphql
- Upgrade to the fixed version 0.312.3 using: pip install strawberry-graphql==0.312.3
- Verify the upgrade was successful: pip show strawberry-graphql | grep Version
- If using a requirements file, update the version constraint to: strawberry-graphql==0.312.3
- Restart any services or applications using the library to ensure the new version is loaded
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Strawberry Graphql
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35526 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-35526 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data