{"answers":{"affected":"3 open source packages ship an affected version, including strawberry-graphql.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107727 exists.","fix":"Upgrade strawberry-graphql to 0.327.2 or later.","what":"CVE-2026-107727 is a low-severity denial of service vulnerability in strawberry-graphql strawberry, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-107727 and fix it if it is affected.\n\nWhat it is: CVE-2026-107727 is a low-severity denial of service vulnerability in strawberry-graphql strawberry, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107727 exists.\n\nAffected packages and fixed versions:\n- strawberry-graphql (PyPI): affected from 0.312.3; fixed in 0.327.2\n- strawberry-graphql (PyPI): affected from 0.312.3; fixed in 0.327.2\n- strawberry-graphql (PyPI): affected from 0.312.3; fixed in 0.327.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-107727/ (Markdown: https://insights.sbomify.com/CVE-2026-107727/index.md)","id":"CVE-2026-107727","markdown":"https://insights.sbomify.com/CVE-2026-107727/index.md","name":"CVE-2026-107727","record":{"aliases":["GHSA-m952-2w3f-6r8h","PYSEC-2026-4302"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Python GraphQL library","requires_auth":"none","summary":"Attackers can exhaust subscription slots on persistent WebSocket connections in Strawberry GraphQL, blocking legitimate operations when per-connection limits are configured.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Strawberry legacy graphql-ws retains naturally completed subscription slots","id":"CVE-2026-107727","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"Strawberry GraphQL: Synchronous permission checks can treat an awaitable authorization result as truthy","id":"CVE-2026-107728"},"packages":[{"ecosystem":"PyPI","fixed":["0.327.2"],"introduced":["0.312.3"],"last_affected":[],"package":"strawberry-graphql","purl":null,"source":"GHSA-m952-2w3f-6r8h"},{"ecosystem":"PyPI","fixed":["0.327.2"],"introduced":["0.312.3"],"last_affected":[],"package":"strawberry-graphql","purl":"pkg:pypi/strawberry-graphql","source":"GHSA-m952-2w3f-6r8h"},{"ecosystem":"PyPI","fixed":["0.327.2"],"introduced":["0.312.3"],"last_affected":[],"package":"strawberry-graphql","purl":"pkg:pypi/strawberry-graphql","source":"PYSEC-2026-4302"}],"prev":{"headline":"Hazelcast: Arbitrary member memory access by low-privileged client","id":"CVE-2026-107726"},"products":["strawberry"],"published":"2026-10-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-13","vendors":["strawberry-graphql"]},"summary":"Attackers can exhaust subscription slots on persistent WebSocket connections in Strawberry GraphQL, blocking legitimate operations when per-connection limits are configured.","url":"https://insights.sbomify.com/CVE-2026-107727/"}