Vulnerability in strawberry-graphql (CVE-2026-107727)
Summary
Vulnerability in strawberry-graphql (CVE-2026-107727). Risk of unauthorized operations or information disclosure. Exploitable via complete. Mitigation: upgrade to 0.327.2 or later.
Original description
The description as published by the source.
Summary
Strawberry's legacy graphql-ws subscription handler can retain task and subscription bookkeeping after a one-shot subscription has naturally sent its complete message. When the application configures max_subscriptions_per_connection, the handler counts those completed operations in len(self.tasks). A client that uses distinct operation IDs can therefore reach the configured subscription limit even though the earlier subscriptions have already completed, causing subsequent legitimate subscriptions on the same persistent WebSocket connection to receive Subscription limit reached.
This is a conditional connection-level availability and resource-accounting issue. It requires explicit use of the legacy graphql-ws protocol, a persistent WebSocket connection, one-shot subscriptions that naturally complete, and a configured max_subscriptions_per_connection limit. It is not an unconditional issue in a default Strawberry installation and is distinct from the previously fixed single-connection infinite-subscription issue.
Details
The audited snapshot is Strawberry 0.324.4, commit c3caabd1188acda62045e7fd9ba9e37ac430cf96. The relevant implementation is in [[strawberry/subscriptions/protocols/graphql_ws/handlers.py](https://github.com/strawberry-graphql/strawberry/blob/c3caabd1188acda62045e7fd9ba9e37ac430cf96/strawberry/subscriptions/protocols/graphql_ws/handlers.py)](https://github.com/strawberry-graphql/strawberry/blob/c3caabd1188acda62045e7fd9ba9…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-107727 has been found in strawberry-graphql.
Attackers can target a specific entry point like complete over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/10.
What to do: upgrade strawberry-graphql to 0.327.2 or later.
If unsure, ask your IT team or search "strawberry-graphql CVE-2026-107727" on the vendor's site.
CVE-2026-107727 (strawberry-graphql) — CWE-400 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: complete / max_subscriptions_per_connection / c3caabd1188acda62045e7fd9ba9e37ac430cf96 / self.tasks
Patched: 0.327.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-400) exists in strawberry-graphql. Attackers reach the vulnerable code path via complete without authentication.
Check the vendor advisory for the affected versions of strawberry-graphql. Attack surface: complete / max_subscriptions_per_connection / c3caabd1188acda62045e7fd9ba9e37ac430cf96 / self.tasks.
Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.
Update to 0.327.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'strawberry-graphql' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'strawberry-graphql' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
strawberry-graphqlを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade strawberry-graphql to 0.327.2ステージング環境で 0.327.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。