{"answers":{"affected":"3 open source packages ship an affected version, including strawberry-graphql.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107728 exists.","fix":"Upgrade strawberry-graphql to 0.326.1 or later.","what":"CVE-2026-107728 is a high-severity authentication bypass vulnerability in strawberry-graphql strawberry, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-107728 and fix it if it is affected.\n\nWhat it is: CVE-2026-107728 is a high-severity authentication bypass vulnerability in strawberry-graphql strawberry, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107728 exists.\n\nAffected packages and fixed versions:\n- strawberry-graphql (PyPI): affected from 0.217.0; fixed in 0.326.1\n- strawberry-graphql (PyPI): affected from 0.217.0; fixed in 0.326.1\n- strawberry-graphql (PyPI): affected from 0.217.0; fixed in 0.326.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-107728/ (Markdown: https://insights.sbomify.com/CVE-2026-107728/index.md)","id":"CVE-2026-107728","markdown":"https://insights.sbomify.com/CVE-2026-107728/index.md","name":"CVE-2026-107728","record":{"aliases":["GHSA-pfvf-fwfp-25mp","PYSEC-2026-4303","ROOT-APP-PYPI-CVE-2026-107728"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"GraphQL library","requires_auth":"none","summary":"Attackers can bypass permission checks in synchronous GraphQL resolvers if custom permissions return unawaited awaitables, allowing unauthorized access to protected data.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Strawberry GraphQL: Synchronous permission checks can treat an awaitable authorization result as truthy","id":"CVE-2026-107728","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"SumatraPDF: Unsigned-to-signed hdrLen validation bypass in SumatraPDF MOBI parsing causes out-of-bounds read","id":"CVE-2026-107729"},"packages":[{"ecosystem":"PyPI","fixed":["0.326.1"],"introduced":["0.217.0"],"last_affected":[],"package":"strawberry-graphql","purl":null,"source":"GHSA-pfvf-fwfp-25mp"},{"ecosystem":"PyPI","fixed":["0.326.1"],"introduced":["0.217.0"],"last_affected":[],"package":"strawberry-graphql","purl":"pkg:pypi/strawberry-graphql","source":"GHSA-pfvf-fwfp-25mp"},{"ecosystem":"PyPI","fixed":["0.326.1"],"introduced":["0.217.0"],"last_affected":[],"package":"strawberry-graphql","purl":"pkg:pypi/strawberry-graphql","source":"PYSEC-2026-4303"}],"prev":{"headline":"Strawberry legacy graphql-ws retains naturally completed subscription slots","id":"CVE-2026-107727"},"products":["strawberry"],"published":"2026-10-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-14","vendors":["strawberry-graphql"]},"summary":"Attackers can bypass permission checks in synchronous GraphQL resolvers if custom permissions return unawaited awaitables, allowing unauthorized access to protected data.","url":"https://insights.sbomify.com/CVE-2026-107728/"}