Categories
CVE-2026-47707 medium CVSS 5.3

Vulnerability in strawberry-graphql (CVE-2026-47707)

Summary

Vulnerability in strawberry-graphql (CVE-2026-47707). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.315.7 or later.

Original description

The description as published by the source.

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.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-47707 has been found in strawberry-graphql.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade strawberry-graphql to 0.315.7 or later.
If unsure, ask your IT team or search "strawberry-graphql CVE-2026-47707" on the vendor's site.

CVE-2026-47707 (strawberry-graphql) — CWE-400 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.315.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-400) exists in strawberry-graphql.

📍 Affected scope

Check the vendor advisory for the affected versions of strawberry-graphql.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.315.7.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'strawberry-graphql' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'strawberry-graphql' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で strawberry-graphql を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade strawberry-graphql to 0.315.7

    ステージング環境で 0.315.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip strawberry-graphql
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.315.7"}]}]
PyPI strawberry-graphql
[{"type":"ECOSYSTEM","events":[{"introduced":"0.172.0"},{"fixed":"0.315.7"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details