cve.bz

CVE-2026-107727 strawberry-graphql strawberry: Uncontrolled Resource Consumption

3.7 lowEPSS 0.4%Fix available

Low (3.7) in strawberry-graphql strawberry. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in strawberry-graphql 0.327.2.

On this page
Strawberry GraphQL is a library for creating GraphQL APIs. From 0.312.3 until 0.327.2, the legacy graphql-ws subscription handler in strawberry/subscriptions/protocols/graphql_ws/handlers.py does not remove naturally completed operations from self.tasks and self.subscriptions. When max_subscriptions_per_connection is configured, a client on a persistent WebSocket connection can use distinct operation IDs for one-shot subscriptions to fill the connection's configured slots even after those subscriptions send complete, causing later legitimate operations on that connection to be rejected with Subscription limit reached. The modern graphql-transport-ws protocol and deployments without the configured per-connection cap are not affected. This issue is fixed in version 0.327.2.

Severity

CVSS 3.1

3.7 low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 38th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • strawberry-graphql (PyPI): fixed in 0.327.2

Ask an AI about this CVE

Show the promptExplain CVE-2026-107727 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107727?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107727?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-107727 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
strawberry-graphql strawberry>= 0.312.3, < 0.327.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-m952-2w3f-6r8hPyPIstrawberry-graphql>=0.312.3 <0.327.20.327.2
PYSEC-2026-4302PyPIstrawberry-graphql>=0.312.3 <0.327.20.327.2

Red Hat

Red Hat rates this Low.

Red Hat's statement

A LOW severity denial-of-service flaw was found in the legacy graphql-ws subscription handler of strawberry-graphql, a Python GraphQL library included in the Red Hat Exploit Intelligence vulnerability-analysis-rhel9 container. When a limit on subscriptions per connection is configured, the legacy handler does not remove naturally completed operations from its internal tracking. A remote client on a persistent WebSocket connection can send many short-lived subscription requests with distinct operation IDs to fill the connection's configured subscription slots even after those subscriptions complete, causing subsequent legitimate operations on that connection to be rejected. Exploitation requires both the legacy graphql-ws protocol and an explicitly configured per-connection subscription limit; the modern graphql-transport-ws protocol and deployments without the configured cap are not affected. Within Red Hat, the only product in scope is the Exploit Intelligence vulnerability-analysis-rhel9 container, whose update stream is not in full support scope, so the affect is recorded as out of support scope and no Red Hat fix is planned for that stream. The Red Hat severity of LOW (CVSS 3.1 score 3.7) is consistent with the upstream assessment.

Red Hat's mitigation

Affected deployments can mitigate this issue by migrating from the legacy graphql-ws subscription protocol to the modern graphql-transport-ws protocol, which is not affected, or by removing the configured max_subscriptions_per_connection limit, since deployments without the per-connection cap are not affected. Because the exhausted subscription slots are tracked per WebSocket connection, closing the affected connection restores capacity on new connections. Upstream fixed this issue in strawberry-graphql 0.327.2; the affected Red Hat Exploit Intelligence stream is out of support scope, so no Red Hat update is planned for it.

ProductPackageStateAdvisory
Exploit Intelligenceexploit-intelligence/vulnerability-analysis-rhel9Out of support scope

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-107727.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON