Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 3.7amended

Strawberry legacy graphql-ws retains naturally completed subscription slots

CVE-2026-107727GHSA-m952-2w3f-6r8h

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (strawberry-graphql 0.327.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
3.7 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
  • CVE-2026-107727: 0.43% estimated exploitation activity in the next 30 days; percentile 37.31 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 maxsubscriptionsperconnection, 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 maxsubscriptionsperconnection limit. It is not an unconditional issue in a default Strawberry installation and is distinct from the previously fixed…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-m952-2w3f-6r8h

  2. Revision 2 · amended ·

    Amended from osv record GHSA-m952-2w3f-6r8h

  3. Revision 1 · created ·

    Published from ghsa record GHSA-m952-2w3f-6r8h

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-107727

Advisory: Strawberry legacy graphql-ws retains naturally completed subscription slots
IDs: CVE-2026-107727, GHSA-m952-2w3f-6r8h
Record: https://patchnext.com/advisories/cve-2026-107727 (revision 3, source checked 26 Oct 2026, 13:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: strawberry-graphql 0.327.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI strawberry-graphql: affected >= 0.312.3, < 0.327.2; fixed in 0.327.2

## Suggested inspection (read-only)
- `python -m pip show strawberry-graphql`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on strawberry-graphql.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-m952-2w3f-6r8h (GitHub-reviewed advisory GHSA-m952-2w3f-6r8h lists affected ranges: PyPI strawberry-graphql >=0.312.3 <0.327.2)
- Verified: https://osv.dev/vulnerability/GHSA-m952-2w3f-6r8h (OSV record GHSA-m952-2w3f-6r8h lists affected ranges: PyPI strawberry-graphql >=0.312.3 <0.327.2 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…