Strawberry GraphQL's Bypass of MaxAliasesLimiter via Fragment Spreads leading to GraphQL Alias Amplification
CVE-2026-47707GHSA-fr49-mhgj-crfc
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (strawberry-graphql 0.315.7), 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.
Affected packages
PyPI strawberry-graphql
- Affected
- >= 0.172.0, <= 0.315.6
- Fixed in
- 0.315.7
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-fr49-mhgj-crfc lists affected ranges: PyPI strawberry-graphql >=0.172.0 <0.315.7 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-fr49-mhgj-crfc lists affected ranges: PyPI strawberry-graphql >=0.172.0 <=0.315.6
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- EPSS
- CVE-2026-47707: 0.47% estimated exploitation activity in the next 30 days; percentile 40.37 (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 The MaxAliasesLimiter extension in Strawberry fails to account for the multiplicative/amplification effect of FragmentSpreadNode. While it correctly counts static aliases within the AST it does not consider how many times a fragments internal aliases are expanded during execution. this allows an attacker to bypass alias limits and force the server to resolve and render a significantly higher number of aliases than allowed, potentially leading to a dos via resource exhaustion. Details The current implementation of alias counting in strawberry/extensions/maxaliases.py uses a static approach When a FragmentSpread is used multiple times, the actual number of aliases processed by the execution engine is Total Aliases = query aliases + (num of spreads aliases within fragment) Because Strawberry only performs a static sum of the text, it misses this multiplication PoC server code payloads Impact An attacker can bypass security constraints to cause Application-level DOS. By staying…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-fr49-mhgj-crfc
- Revision 1 · created ·
Published from osv record GHSA-fr49-mhgj-crfc
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-47707 Advisory: Strawberry GraphQL's Bypass of MaxAliasesLimiter via Fragment Spreads leading to GraphQL Alias Amplification IDs: CVE-2026-47707, GHSA-fr49-mhgj-crfc Record: https://patchnext.com/advisories/cve-2026-47707 (revision 2, source checked 26 Oct 2026, 13:45 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.3) 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.315.7. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI strawberry-graphql: affected >= 0.172.0, <= 0.315.6; fixed in 0.315.7 ## 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://osv.dev/vulnerability/GHSA-fr49-mhgj-crfc (OSV record GHSA-fr49-mhgj-crfc lists affected ranges: PyPI strawberry-graphql >=0.172.0 <0.315.7 (fixed)) - Verified: https://github.com/advisories/GHSA-fr49-mhgj-crfc (GitHub-reviewed advisory GHSA-fr49-mhgj-crfc lists affected ranges: PyPI strawberry-graphql >=0.172.0 <=0.315.6) Commands are suggestions: review each one before running it.
Loading voting…