Quick answers
- Is CVE-2026-107728 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-107728 being exploited in the wild.
- How severe is CVE-2026-107728?
- High severity, with a CVSS score of 7.5, published 8 October 2026.
- Which products and versions are affected?
- strawberry-graphql (PyPI) >= 0.217.0, <= 0.326.0, ECOSYSTEM:introduced=0.217.0,fixed=0.326.1.
- Is there a fix for CVE-2026-107728?
- Yes. strawberry-graphql (PyPI): upgrade to 0.326.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-107728 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-107728?
- Check whether you run strawberry-graphql (PyPI) or Strawberry GraphQL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- strawberry-graphql (PyPI): upgrade to 0.326.1 or later
pip install "strawberry-graphql>=0.326.1"
Technical details
The vulnerability exists in PermissionExtension.resolve() which evaluates custom permission checks for truthiness. When has_permission() is a plain def (not async def) but returns an awaitable, the synchronous path does not await it and treats the awaitable as truthy (since all awaitables are truthy in Python), allowing access even when the awaitable would resolve to False. This affects synchronous field resolvers regardless of whether execute_sync() or execute() is called. The fix raises an error if an awaitable is encountered on the synchronous path instead of granting access.
Affected products
- Strawberry GraphQL
Identifiers
- CVE-2026-107728
- GHSA-pfvf-fwfp-25mp
- PYSEC-2026-4303
Timeline
- 2026-10-09: disclosed