dbcve.org
Strawberry GraphqlApplication · Strawberry

CVE-2026-35523

HIGH · 7.5 CVSS v3.1 Published 2026-04-07
Fix available
A fix is available. Upgrade to 0.312.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Strawberry GraphQL is a library for creating GraphQL APIs. Strawberry up until version 0.312.3 is vulnerable to an authentication bypass on WebSocket subscription endpoints. The legacy graphql-ws subprotocol handler does not verify that a connection_init handshake has been completed before processing start (subscription) messages. This allows a remote attacker to skip the on_ws_connect authentication hook entirely by connecting with the graphql-ws subprotocol and sending a start message directly, without ever sending connection_init. 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 confidence

Strawberry GraphQL's legacy graphql-ws subprotocol handler fails to verify that the connection_init handshake has been completed before processing start (subscription) messages. This allows unauthenticated remote attackers to bypass the on_ws_connect authentication hook by connecting with the graphql-ws subprotocol and sending a start message directly without ever sending connection_init.

MitigationUpgrade Strawberry GraphQL to version 0.312.3 or later to remediate this authentication bypass vulnerability.

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
Affected:< 0.312.3

CVSS 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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Strawberry GraphQL version
    Run `pip show strawberry-graphql` or inspect your requirements.txt/pyproject.toml for the installed version
    Affected if The installed version is lower than 0.312.3
  2. Verify WebSocket subscription support is enabled
    Inspect your GraphQL server configuration for WebSocket subscription transport (look for Subscription schema configuration or websocket=True in subscription settings)
    Affected if WebSocket subscriptions are enabled and the graphql-ws subprotocol is in use
  3. Confirm on_ws_connect authentication hook is in use
    Search your codebase for on_ws_connect parameter in GraphQL subscription or WebSocket configuration
    Affected if An on_ws_connect hook is configured for authentication (this hook is what gets bypassed)
  4. Identify graphql-ws subprotocol usage
    Check your WebSocket connection setup for 'graphql-ws' subprotocol (as opposed to 'graphql-transport-ws')
    Affected if The graphql-ws subprotocol is being used for WebSocket connections

You are affected if Strawberry GraphQL version is below 0.312.3 and your server accepts graphql-ws subprotocol connections for WebSocket subscriptions, allowing the on_ws_connect authentication to be bypassed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 0.312.3 or later
Fixed in 0.312.3
Interim mitigation

Upgrade Strawberry GraphQL to version 0.312.3 or later to remediate this authentication bypass vulnerability.

Recommended fix High confidence

0.312.3

  1. Check the current installed version of strawberry-graphql with: pip show strawberry-graphql or pip freeze | grep strawberry
  2. Upgrade to version 0.312.3 or later using: pip install strawberry-graphql>=0.312.3
  3. Verify the upgrade was successful by running: pip show strawberry-graphql and confirming the version number
  4. Test that WebSocket subscriptions still function correctly with your authentication configuration

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Strawberry Graphql Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35523 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-35523 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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