All vulnerabilities
CVE-2026-107728GHSA-pfvf-fwfp-25mpPYSEC-2026-4303

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

strawberry-graphql strawberry-graphqlpipLibraries & packages
Open in ThreatlineRecord JSON
CVSS
7.5High
ExploitationPublic exploit codeCISA's assessment says proof of concept code is public, assessed 14 Oct 2026. Not in the KEV catalogCISA via CVE List
Exploit odds (EPSS)0.35%Chance of exploitation activity in the next 30 days, higher than 27% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in0.326.1Fixed versionGitHub
Published8 Oct 2026Updated 15 Oct 2026CVE List

What fixes it

  • 0.326.1strawberry-graphql, pipGitHub
  • 0.326.1strawberry-graphql, PyPIOSVpip install "strawberry-graphql>=0.326.1"

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Description

Summary

PermissionExtension.resolve() evaluates the return value of has_permission() for truthiness on the synchronous path. supports_sync only classifies a permission as asynchronous when has_permission is declared with async def (via inspect.iscoroutinefunction), so a plain def that returns an awaitable is treated as synchronous. An awaitable is always truthy, so the check passes even when it resolves to False and the protected resolver runs.

The resolve path is chosen by the field resolver, not by the execution method, so any field with a synchronous resolver is affected under both execute_sync() and execute(). Permissions declared with async def has_permission(), or a plain def returning a boolean, are not affected.

Details

The affected code is PermissionExtension.resolve() in strawberry/permission.py. A permission attached to a field whose has_permission is a normal def returning an awaitable reaches this path; the awaitable is never awaited and its truthiness grants access. resolve_async() is not affected because it uses await_maybe().

PoC

import strawberry
from strawberry.permission import BasePermission


class DenyViaAwaitable(BasePermission):
    message = "denied"

    def has_permission(self, source, info, **kwargs):
        async def result():
            return False

        return result()


@strawberry.type
class Query:
    @strawberry.field(permission_classes=[DenyViaAwaitable])
    def secret(self) -> str:
        return "secret"


schema = strawberry.Schema(Query)
print(schema.execute_sync("{ secret }").data)  # {'secret': 'secret'} instead of a permission error

Impact

An application using a custom permission whose has_permission is a normal def returning an awaitable can unintentionally grant access to the protected field. Standard permissions (a def returning a boolean, or an async def) are not affected, so exploitability depends on the application using this specific permission shape.

Fix

The synchronous path now fails closed: if has_permission() returns an awaitable, an error is raised instead of granting access.

Text from GitHub Advisory Database

Affected versions 53

  • strawberry-graphql, pip>= 0.217.0, <= 0.326.0GitHub
  • strawberryaffected: >= 0.217.0, < 0.326.1CVE List
  • strawberry-graphql, PyPIfrom 0.217.0, fixed in 0.326.1OSV
  • strawberry-graphql, PyPI0.217.0OSV
  • strawberry-graphql, PyPI0.217.1OSV
  • strawberry-graphql, PyPI0.218.0OSV
  • strawberry-graphql, PyPI0.218.0.dev1705418681OSV
  • strawberry-graphql, PyPI0.218.1OSV
  • strawberry-graphql, PyPI0.219.0OSV
  • strawberry-graphql, PyPI0.219.1OSV
  • strawberry-graphql, PyPI0.219.2OSV
  • strawberry-graphql, PyPI0.220.0OSV
  • strawberry-graphql, PyPI0.220.0.dev1709543239OSV
  • strawberry-graphql, PyPI0.221.0OSV
  • strawberry-graphql, PyPI0.221.0.dev1710955937OSV
  • strawberry-graphql, PyPI0.221.1OSV
  • strawberry-graphql, PyPI0.222.0OSV
  • strawberry-graphql, PyPI0.223.0OSV
  • strawberry-graphql, PyPI0.224.0OSV
  • strawberry-graphql, PyPI0.224.0.dev1711748192OSV
  • strawberry-graphql, PyPI0.224.1OSV
  • strawberry-graphql, PyPI0.224.2OSV
  • strawberry-graphql, PyPI0.225.0OSV
  • strawberry-graphql, PyPI0.225.1OSV
  • strawberry-graphql, PyPI0.226.0OSV
  • strawberry-graphql, PyPI0.226.1OSV
  • strawberry-graphql, PyPI0.226.2OSV
  • strawberry-graphql, PyPI0.227.0OSV
  • strawberry-graphql, PyPI0.227.0.dev1713463204OSV
  • strawberry-graphql, PyPI0.227.0.dev1713475585OSV
  • strawberry-graphql, PyPI0.227.1OSV
  • strawberry-graphql, PyPI0.227.2OSV
  • strawberry-graphql, PyPI0.227.3OSV
  • strawberry-graphql, PyPI0.227.4OSV
  • strawberry-graphql, PyPI0.227.5OSV
  • strawberry-graphql, PyPI0.227.6OSV
  • strawberry-graphql, PyPI0.227.7OSV
  • strawberry-graphql, PyPI0.228.0OSV
  • strawberry-graphql, PyPI0.228.0.dev1713643365OSV
  • strawberry-graphql, PyPI0.229.0OSV
  • strawberry-graphql, PyPI0.229.1OSV
  • strawberry-graphql, PyPI0.229.2OSV
  • strawberry-graphql, PyPI0.229.2.dev1715873118OSV
  • strawberry-graphql, PyPI0.229.2.dev1715881453OSV
  • strawberry-graphql, PyPI0.230.0OSV
  • strawberry-graphql, PyPI0.230.0.dev1716318708OSV
  • strawberry-graphql, PyPI0.231.0OSV
  • strawberry-graphql, PyPI0.231.1OSV
  • strawberry-graphql, PyPI0.232.0OSV
  • strawberry-graphql, PyPI0.232.1OSV
  • strawberry-graphql, PyPI0.232.2OSV
  • strawberry-graphql, PyPI0.233.0OSV
  • strawberry-graphql, PyPI0.233.1OSV

References 6