What’s Vulnerable › Vulnerabilities

CVE-2026-107727: Strawberry legacy graphql-ws retains naturally completed subscription slots

• Severity: low (CVSS 3.7 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.4% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-10-08 · updated 2026-10-13
• Weakness: CWE-400

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.

Affected products

• strawberry-graphql strawberry: from 0.312.3, < 0.327.2

References

• https://github.com/strawberry-graphql/strawberry/commit/24c5e46d57f7ad4f77e6e01fb8ae482dd1c0ff92
• https://github.com/strawberry-graphql/strawberry/pull/4610
• https://github.com/strawberry-graphql/strawberry/releases/tag/0.327.2
• https://github.com/strawberry-graphql/strawberry/security/advisories/GHSA-m952-2w3f-6r8h
• https://github.com/strawberry-graphql/strawberry/security/advisories/GHSA-m952-2w3f-6r8h

Get alerted when CVE-2026-107727 or the next vulnerability affects your stack