{"answers":{"affected":"4 open source packages ship an affected version, including graphql-core.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75508 exists.","fix":"Upgrade graphql-core to a fixed version for your release line: 3.2.12 or 3.3.0rc1.","what":"CVE-2026-75508 is a high-severity vulnerability in graphql-python graphql-core, published on 22 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-75508 and fix it if it is affected.\n\nWhat it is: CVE-2026-75508 is a high-severity vulnerability in graphql-python graphql-core, published on 22 Oct 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75508 exists.\n\nAffected packages and fixed versions:\n- graphql-core (PyPI): affected from 3.2.3; fixed in 3.2.12\n- graphql-core (PyPI): affected from 3.2.3; fixed in 3.2.12\n- graphql-core (PyPI): affected from 3.3.0a3; fixed in 3.3.0rc1\n- graphql-core (PyPI): affected from 3.3.0a3; fixed in 3.3.0rc1\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-75508/ (Markdown: https://insights.sbomify.com/CVE-2026-75508/index.md)","id":"CVE-2026-75508","markdown":"https://insights.sbomify.com/CVE-2026-75508/index.md","name":"CVE-2026-75508","record":{"aliases":["DEBIAN-CVE-2026-75508","GHSA-r77w-qph3-7vf8","ROOT-APP-PYPI-CVE-2026-75508","UBUNTU-CVE-2026-75508"],"analysis":null,"analysis_generated_by":null,"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:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"GraphQL-core is a Python port of the GraphQL.js reference implementation. From 3.2.3 until 3.2.12 and 3.3.0rc1, the parser's max_tokens limit in Parser.advance_lexer counts only non-comment tokens returned after Lexer.lookahead skips comments. Each skipped comment is still allocated as a Token and retained through token.next and token.prev, allowing a highly compressible comment-padded GraphQL document to pass a low token limit while consuming memory. An unauthenticated remote attacker can exhaust worker memory before AST-based depth or complexity controls run. This issue is fixed in versions 3.2.12 and 3.3.0rc1.","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":"GraphQL-core: Denial of service via comment tokens bypassing the parser's max_tokens limit","id":"CVE-2026-75508","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":null,"year":"2026"},"n_packages":4,"n_references":5,"next":{"headline":"joserfc claim-validation bypass via array-typed single-string claims (iss/sub/jti)","id":"CVE-2026-75509"},"packages":[{"ecosystem":"PyPI","fixed":["3.2.12"],"introduced":["3.2.3"],"last_affected":[],"package":"graphql-core","purl":null,"source":"GHSA-r77w-qph3-7vf8"},{"ecosystem":"PyPI","fixed":["3.2.12"],"introduced":["3.2.3"],"last_affected":[],"package":"graphql-core","purl":"pkg:pypi/graphql-core","source":"GHSA-r77w-qph3-7vf8"},{"ecosystem":"PyPI","fixed":["3.3.0rc1"],"introduced":["3.3.0a3"],"last_affected":[],"package":"graphql-core","purl":null,"source":"GHSA-r77w-qph3-7vf8"},{"ecosystem":"PyPI","fixed":["3.3.0rc1"],"introduced":["3.3.0a3"],"last_affected":[],"package":"graphql-core","purl":"pkg:pypi/graphql-core","source":"GHSA-r77w-qph3-7vf8"}],"prev":{"headline":"GraphQL-core: Denial of service via quadratic complexity in the OverlappingFieldsCanBeMerged validation rule","id":"CVE-2026-75507"},"products":["graphql-core"],"published":"2026-10-22","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":"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-29","vendors":["graphql-python"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-75508/"}