CVE-2026-107727 is a low-severity (CVSS 3.7) Uncontrolled Resource Consumption vulnerability. No vendor fix is recorded yet; mitigation options are listed below.
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…
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-107727.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-107727 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 394,415 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Description
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.
Detection & mitigation playbook
VulnerabilityDetect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2026-107727 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
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…
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.Source: Red Hat security advisory for CVE-2026-107727 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2026-107727 in your dependencies?
Find it across , including transitive dependencies.