[ CVE-2026-107728 · Published 8 Oct 2026 ]

Strawberry GraphQL: Synchronous permission checks can treat an awaitable authorization result as truthy

CVSS 7.5 EPSS <1%Fix available

[ Why it matters ]Priority signals

  • Public proof-of-concept exploit exists (CISA SSVC)

[ Description ]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.

[ Fixes ]Fixes and patches

  • strawberry-graphql 0.326.1Fixed version · GitHub Advisories · pip package strawberry-graphql: upgrade to 0.326.1 or later (affected >= 0.217.0, <= 0.326.0)

[ Packages ]Affected open-source packages

  • strawberry-graphql pipAffected >= 0.217.0, <= 0.326.0 · fixed in 0.326.1 · GHSA-pfvf-fwfp-25mp