CVE-2026-107728

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

Published Oct 8, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability in Strawberry GraphQL occurs when a synchronous field resolver is protected by a custom permission that defines has_permission() as a normal function but returns an awaitable. Because the library treats the returned awaitable as a truthy value, the permission check passes even though the awaited result would be false, with insufficient authorization. The flaw is an example of an authorization bypass weakness.

Affected Systems

Affected users are anyone who incorporated strawberry-graphql binaries between versions 0.217.0 and 0.326.1, inclusive. These releases are common in Python projects building GraphQL APIs. The issue does not affect permissions defined with async def has_permission() or synchronous permissions returning a literal boolean.

Risk and Exploitability

The CVSS score of 7.5 indicates a high severity risk. EPSS is not available but the lack of a KEV listing suggests no widespread exploitation yet. However, the flaw can be exploited by an attacker who can inject or manipulate permission functions, potentially leading to unauthorized data access or privilege escalation, especially in environments that rely heavily on custom synchronous resolvers.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply update to strawberry-graphql v0.326.1 or later
  • Verify custom permission functions return a boolean or await correctly
  • If upgrade is not possible, modify permission implementations to avoid returning awaitables during synchronous execution

Generated by OpenCVE AI on October 9, 2026 at 03:06 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-pfvf-fwfp-25mp Strawberry GraphQL: Synchronous permission checks can treat an awaitable authorization result as truthy
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Strawberry
Strawberry strawberry
Vendors & Products Strawberry
Strawberry strawberry
Type Values Removed Values Added
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.
Title Strawberry GraphQL: Synchronous permission checks can treat an awaitable authorization result as truthy
Weaknesses CWE-863
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

Weaknesses
  • CWE-253

    Incorrect Check of Function Return Value

  • CWE-863

    Incorrect Authorization

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 14, 2026, 1:31 AM
Reserved
Oct 8, 2026, 5:21 PM
Status
Awaiting Analysis
Published
Oct 8, 2026, 11:16 PM
Modified
Oct 14, 2026, 2:16 AM
Severity
Important
Public date
Oct 8, 2026, 10:13 PM