Skip to content

← Actionable
High, CVSS 7.5amended

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

CVE-2026-107728GHSA-pfvf-fwfp-25mp

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (strawberry-graphql 0.326.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2026-107728: 0.45% estimated exploitation activity in the next 30 days; percentile 39.07 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary PermissionExtension.resolve() evaluates the return value of haspermission() for truthiness on the synchronous path. supportssync only classifies a permission as asynchronous when haspermission 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 executesync() and execute(). Permissions declared with async def haspermission(), 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 haspermission is a normal def returning an awaitable reaches this path; the awaitable is never awaited and its truthiness grants access.…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-pfvf-fwfp-25mp

  2. Revision 2 · amended ·

    Amended from osv record GHSA-pfvf-fwfp-25mp

  3. Revision 1 · created ·

    Published from ghsa record GHSA-pfvf-fwfp-25mp

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-107728

Advisory: Strawberry GraphQL: Synchronous permission checks can treat an awaitable authorization result as truthy
IDs: CVE-2026-107728, GHSA-pfvf-fwfp-25mp
Record: https://patchnext.com/advisories/cve-2026-107728 (revision 3, source checked 26 Oct 2026, 13:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: strawberry-graphql 0.326.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI strawberry-graphql: affected >= 0.217.0, <= 0.326.0; fixed in 0.326.1

## Suggested inspection (read-only)
- `python -m pip show strawberry-graphql`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on strawberry-graphql.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-pfvf-fwfp-25mp (GitHub-reviewed advisory GHSA-pfvf-fwfp-25mp lists affected ranges: PyPI strawberry-graphql >=0.217.0 <=0.326.0)
- Verified: https://osv.dev/vulnerability/GHSA-pfvf-fwfp-25mp (OSV record GHSA-pfvf-fwfp-25mp lists affected ranges: PyPI strawberry-graphql >=0.217.0 <0.326.1 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…