CVE-2026-107727— Strawberry legacy graphql-ws retains naturally completed subscription slots
Quick assessment
Affected
strawberry-graphql strawberry
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.
Strawberry GraphQL 是一个用于创建 GraphQL API 的库。在版本 0.312.3 到 0.327.2 之间， 中的遗留 graphql-ws 订阅处理器在操作自然完成后，不会将其从 和 中移除。如果配置了 （每连接最大订阅数），持久 WebSocket 连接上的客户端可以通过为一次性订阅使用不同的操作 ID，即使这些订阅已发送完成，也会占满连接配置的最大订阅槽位，导致后续该连接上的合法操作因“达到订阅上限”而被拒绝。现代 graphql-transport-ws 协议以及未配置每连接上限的
Possible ATT&CK Techniques 2 AI
T1499.002 · Service Exhaustion Flood T1499 · Endpoint Denial of Service
Get alerts for future matching vulnerabilities
Log in to subscribe
I. Basic Information for CVE-2026-107727
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
Strawberry legacy graphql-ws retains naturally completed subscription slots
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
Source: CVE Program / CVE List V5
Vulnerability Type
未加控制的资源消耗(资源穷尽)
Source: CVE Program / CVE List V5
Affected Products
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| strawberry-graphql | strawberry | >= 0.312.3, < 0.327.2 | - |
|
II. Public POCs for CVE-2026-107727
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POC
Premium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2026-107727
请登录查看更多情报信息。
Other References for CVE-2026-107727 (4)
-
https://github.com/strawberry-graphql/strawberry/pull/4610 x_refsource_MISC
IV. Related Vulnerabilities
Same product: strawberry
-
CVE-2026-107728
Strawberry GraphQL: Synchronous permission checks can treat -
CVE-2026-47707
Strawberry GraphQL's Bypass of MaxAliasesLimiter via Fragmen -
CVE-2026-45739
Strawberry GraphQL: Default GraphiQL may expose HTTP headers -
CVE-2026-47706
Strawberry GraphQL has a Circular Fragment Reference DOS -
CVE-2026-35523
Authentication bypass in strawberry-graphql via legacy graph
Same vendor: strawberry-graphql
-
CVE-2026-107728
Strawberry GraphQL: Synchronous permission checks can treat -
CVE-2026-47707
Strawberry GraphQL's Bypass of MaxAliasesLimiter via Fragmen -
CVE-2026-45739
Strawberry GraphQL: Default GraphiQL may expose HTTP headers -
CVE-2026-47706
Strawberry GraphQL has a Circular Fragment Reference DOS -
CVE-2026-35523
Authentication bypass in strawberry-graphql via legacy graph
Same weakness: CWE-400
-
CVE-2026-107391
music-metadata: MP4 stsd sample-entry size==0 causes a synch -
CVE-2026-84276
IBM Guardium Data Protection Denial of Service -
CVE-2026-107294
Pydantic AI: Unbounded memory use when downloading remote co -
CVE-2026-61801
github.com/moby/sys/user has a possible DoS via unbounded pa -
CVE-2026-107287
Pydantic AI: Excessive resource use when local web fetching
V. Comments for CVE-2026-107727
No comments yet