# Strawberry legacy graphql-ws retains naturally completed subscription slots

Advisory record · `GHSA-m952-2w3f-6r8h`

- **Identifiers:** `GHSA-m952-2w3f-6r8h` · `CVE-2026-107727` · `PYSEC-2026-4302`
- **State:** Confirmed
- **Severity:** CVSS 3.7 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-400](https://cwe.mitre.org/data/definitions/400.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 9 Oct 2026
- **Updated:** 15 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 9 Oct 2026, 14:07 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `strawberry-graphql` (PyPI): affected `>=0.312.3, <0.327.2`; fixed in `0.327.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Strawberry (PyPI package strawberry-graphql) versions >=0.312.3 and <0.327.2 are affected; upgrade to 0.327.2. The legacy graphql-ws subscription handler keeps completed one-shot subscriptions counted against the per-connection limit set by max_subscriptions_per_connection. A client holding a persistent WebSocket connection can fill those slots with completed operations, so later legitimate subscriptions on that connection get "Subscription limit reached". This requires the legacy graphql-ws protocol and that limit to be configured, and the impact is availability on that connection.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 3.7 Low, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0043, the 37th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:08 UTC: First seen by agentprime
- 31 Oct 2026, 14:08 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-m952-2w3f-6r8h)

## Sources

- [GitHub Advisory Database: GHSA-m952-2w3f-6r8h](https://github.com/advisories/GHSA-m952-2w3f-6r8h)
- [OSV: GHSA-m952-2w3f-6r8h](https://osv.dev/vulnerability/GHSA-m952-2w3f-6r8h)
- <https://github.com/strawberry-graphql/strawberry/security/advisories/GHSA-m952-2w3f-6r8h>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-107727>
- <https://github.com/strawberry-graphql/strawberry/pull/4610>
- <https://github.com/strawberry-graphql/strawberry/commit/24c5e46d57f7ad4f77e6e01fb8ae482dd1c0ff92>
- <https://github.com/strawberry-graphql/strawberry>
- <https://github.com/strawberry-graphql/strawberry/releases/tag/0.327.2>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-m952-2w3f-6r8h>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-m952-2w3f-6r8h/>. Everything for agents: <https://agentprime.io/llms.txt>.