Disclosure summary
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.
Source-reported weakness categories
CWE-863
Source-specific records & product guidance
Sources retain their own attribution and scoring. Follow the original record to confirm affected versions, fixed releases, and configuration conditions.
NIST National Vulnerability Database · NVD-CVE-2026-107728
Open original source · Updated Oct 09, 2026
Only CPE matches marked vulnerable=true are indexed. AND/OR platform conditions must be checked in the original NVD record.
GitHub Reviewed Security Advisories · GHSA-pfvf-fwfp-25mp
Open original source · Updated Oct 09, 2026
Strawberry GraphQL: Synchronous permission checks can treat an awaitable authorization result as truthy
Source severity: HIGH / 0
| Ecosystem | Package | Affected range | First patched |
|---|---|---|---|
| pip | strawberry-graphql | >= 0.217.0, | 0.326.1 |
Original records & references
PUBLISHED 2026-10-08T19:16:58-04:00
MODIFIED 2026-10-09T13:06:17-04:00
INGESTED 2026-10-10T20:55:12-04:00