← Back
CVE-2026-45739
low
CVSS 3.1
Information Disclosure in strawberry-graphql (CVE-2026-45739)
Summary
vulnerability in strawberry-graphql (CVE-2026-45739). Risk of unauthorized operations or information disclosure. Exploitable via ``parameters``. Mitigation: upgrade to `0.315.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-45739** has been found in strawberry-graphql.
Attackers can target a specific entry point like ``parameters`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.1/10.
What to do: upgrade strawberry-graphql to **0.315.4** or later.
If unsure, ask your IT team or search "strawberry-graphql CVE-2026-45739" on the vendor's site.
CVE-2026-45739 (strawberry-graphql) — CWE-200 / CVSS v3 3.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `parameters` / `history.replaceState` / `updateURL` / `onEditHeaders`
Patched: `0.315.4` — 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
**information disclosure** (CWE-200) exists in strawberry-graphql. Attackers reach the vulnerable code path via ``parameters`` without authentication.
📍 Affected scope
strawberry-graphql — . Attack surface: `parameters` / `history.replaceState` / `updateURL` / `onEditHeaders`.
🔥 Severity
Severity: Low (CVSS 3.1/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.315.4**.
🛡️ 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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'strawberry-graphql' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `strawberry-graphql` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade strawberry-graphql to 0.315.4ステージング環境で 0.315.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
strawberry-graphql
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.315.4"}]}]
PyPI
strawberry-graphql
[{"type":"ECOSYSTEM","events":[{"introduced":"0.288.4"},{"fixed":"0.315.4"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-45739
- package https://github.com/strawberry-graphql/strawberry
- web https://github.com/strawberry-graphql/strawberry/security/advisories/GHSA-x97m-qp5c-w9xj
- web https://github.com/strawberry-graphql/strawberry/issues/4398
- web https://github.com/strawberry-graphql/strawberry/pull/2842
- web https://github.com/advisories/GHSA-x97m-qp5c-w9xj
- web https://github.com/strawberry-graphql/strawberry/commit/9315ef80a621ae50ca0bc5c82f560ca4ee7e47a9
- web https://github.com/strawberry-graphql/strawberry/releases/tag/0.315.4