Vulnerability · Published Oct 8, 2026 · Assigned by GitHub_M

CVE-2026-107728Strawberry GraphQL: Synchronous permission checks can treat an awaitable authorization result as truthy

High 7.5

In plain English

A high-severity incorrect authorization in strawberry from strawberry-graphql. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 39% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.5High
Exploit odds (30 days)0.4%top 60.8% of all CVEs
Exploited in the wildNo reportsCISA SSVC: poc
Attack toolingNoneno public tooling known

Official description

Strawberry GraphQL is a library for creating GraphQL APIs. From 0.217.0 until 0.326.1, PermissionExtension.resolve() on a synchronous field resolver evaluates the result of has_permission() for truthiness. When a custom permission declares has_permission() as a normal function but returns an awaitable, supports_sync does not classify it as asynchronous, the awaitable is not awaited, and its inherently truthy object value permits the protected resolver to run even when the result would resolve to false. This affects synchronous field resolvers under both execute_sync() and execute(); permissions declared with async def has_permission() and synchronous permissions returning a boolean are not affected. This issue is fixed in version 0.326.1.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
PyPIstrawberry-graphql0.326.1GHSA-pfvf-fwfp-25mp
PyPIstrawberry-graphql0.326.1PYSEC-2026-4303

Affected products (as reported)

VendorProductVersions
strawberry-graphql strawberry >= 0.217.0, < 0.326.1

Weakness: CWE-863 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

References