CVE-2026-107728Strawberry GraphQL: Synchronous permission checks can treat an awaitable authorization result as truthy
Updated under an hour ago ()
Does this affect you?
It affects strawberry-graphql strawberry. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.35%, higher than 27% of scored CVEs.
Do this next
Free account, 1 product
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.
- CVSS
- 7.5 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Weakness (CWE)
- CWE-863
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.35% (percentile 27)
- Assigned by
- GitHub_M
- NVD analysis
- Awaiting Analysis
- Record last updated
- Oct 14, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
strawberry-graphql strawberry strawberry_graphql:strawberry (from the name) | from 0.217.0, < 0.326.1 | CNA record |
References
- https://github.com/strawberry-graphql/strawberry/security/advisories/GHSA-pfvf-fwfp-25mpx-refsource-confirm
- https://github.com/strawberry-graphql/strawberry/pull/4605x-refsource-misc
- https://github.com/strawberry-graphql/strawberry/commit/2ebb79796c0e5ebb43cae1abd2b5a21363b1c00ex-refsource-misc
- https://github.com/strawberry-graphql/strawberry/releases/tag/0.326.1x-refsource-misc
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.