Skip to main content
VulnerabilityPublished

CVE-2026-35526: strawberry · Unthrottled Resource Allocation

Affects strawberrySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 0.312.3 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.312.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade strawberry and strawberry-graphql/strawberry to 0.312.3.

Affected software

ProductAffectedFixed in
strawberry-graphqlstrawberryAffected
  • <0.312.3
Fixed in
  • 0.312.3
PyPIstrawberry-graphql/strawberrypkg:pypi/strawberry-graphql/strawberryOther threatsAffected
  • <0.312.3
Fixed in
  • 0.312.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Strawberry GraphQL version 0.312.3. Users should upgrade to this version or later to remediate the vulnerability. No other official mitigation or temporary workaround is documented. Patch status is confirmed by the vendor advisory stating the issue is fixed in 0.312.3.

Description

CVE-2026-35526 is a high-severity vulnerability in Strawberry GraphQL versions prior to 0.312.3. The issue arises from the WebSocket subscription handlers, which allocate resources without limiting the number of active subscriptions per connection. An unauthenticated attacker can exploit this by opening a WebSocket connection and flooding subscribe messages, causing unbounded resource consumption. This leads to server degradation or an out-of-memory (OOM) crash. The vulnerability is fixed in version 0.312.3.

References

Community reviews

Loading reviews…