Description
Strawberry GraphQL is a library for creating GraphQL APIs. In versions 0.172.0 through0.315.6, 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. Version 0.315.7 contains a fix for the issue.
Published: 2026-06-04
Score: 5.3 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The MaxAliasesLimiter extension in strawberry-graphql does not correctly account for the amplification effect of fragment spreads in GraphQL queries. A malicious query can therefore bypass the configured alias limit and force the server to resolve and render a far larger number of aliases than intended, leading to excessive CPU and memory usage. This can cause a denial of service by exhausting server resources.

Affected Systems

Affected products are the strawberry-graphql Python library, versions from 0.172.0 up to and including 0.315.6. Users running any of these releases that use the MaxAliasesLimiter extension are vulnerable. The issue is fixed in 0.315.7 and later releases.

Risk and Exploitability

The CVSS score is 5.3, classifying the vulnerability as medium severity. No EPSS score is available, and it is not listed in the CISA KEV catalog, suggesting no publicly known exploits at the time of publication. The vulnerability is likely exploitable via a crafted GraphQL query sent to the server over HTTP, where the attacker provides a query containing many fragment spreads that multiply the alias count beyond the limit. The exploit requires the MaxAliasesLimiter to be enabled.

Generated by OpenCVE AI on June 4, 2026 at 15:21 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade strawberry-graphql to version 0.315.7 or newer to apply the patch that prevents alias amplification.
  • Verify that the MaxAliasesLimiter extension is active and that the alias limit configuration matches your security policy after the upgrade.
  • As a temporary countermeasure, consider tightening the maximum alias count or implementing additional query complexity limits at the GraphQL server to reduce the potential for resource exhaustion until the fix is applied.

Generated by OpenCVE AI on June 4, 2026 at 15:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-fr49-mhgj-crfc Strawberry GraphQL's Bypass of MaxAliasesLimiter via Fragment Spreads leading to GraphQL Alias Amplification
History

Thu, 04 Jun 2026 15:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 04 Jun 2026 14:30:00 +0000

Type Values Removed Values Added
Description Strawberry GraphQL is a library for creating GraphQL APIs. In versions 0.172.0 through0.315.6, 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. Version 0.315.7 contains a fix for the issue.
Title Strawberry GraphQL's Bypass of MaxAliasesLimiter via Fragment Spreads leading to GraphQL Alias Amplification
Weaknesses CWE-400
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-06-04T15:06:13.934Z

Reserved: 2026-05-19T21:29:25.481Z

Link: CVE-2026-47707

cve-icon Vulnrichment

Updated: 2026-06-04T15:05:42.549Z

cve-icon NVD

Status : Undergoing Analysis

Published: 2026-06-04T15:16:55.283

Modified: 2026-06-04T15:35:18.623

Link: CVE-2026-47707

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-06-04T15:30:17Z

Weaknesses