{"answers":{"affected":"4 open source packages ship an affected version, including graphql-core.","exploited":"There is no known exploitation of CVE-2026-75507 in the wild and no public exploit code.","fix":"Upgrade graphql-core to a fixed version for your release line: 3.2.12 or 3.3.0rc1.","what":"CVE-2026-75507 is a high-severity vulnerability in graphql-python graphql-core, published on 22 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-75507 and fix it if it is affected.\n\nWhat it is: CVE-2026-75507 is a high-severity vulnerability in graphql-python graphql-core, published on 22 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-75507 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- graphql-core (PyPI): affected from 3.0.0; fixed in 3.2.12\n- graphql-core (PyPI): affected from 3.0.0; fixed in 3.2.12\n- graphql-core (PyPI): affected from 3.3.0a1; fixed in 3.3.0rc1\n- graphql-core (PyPI): affected from 3.3.0a1; 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-75507/ (Markdown: https://insights.sbomify.com/CVE-2026-75507/index.md)","id":"CVE-2026-75507","markdown":"https://insights.sbomify.com/CVE-2026-75507/index.md","name":"CVE-2026-75507","record":{"aliases":["DEBIAN-CVE-2026-75507","GHSA-vj8h-fx38-h3vc","ROOT-APP-PYPI-CVE-2026-75507","UBUNTU-CVE-2026-75507"],"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-407","name":"Inefficient Algorithmic Complexity"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"GraphQL-core is a Python port of the GraphQL.js reference implementation. From 3.0.0 until 3.2.12 and 3.3.0rc1, the OverlappingFieldsCanBeMerged rule in specified_rules repeatedly compares fields that share response names and recursively re-compares flattened inline fragments during the validation phase. The prior named-fragment memoization does not cover this path, so nested repeated inline fragments can drive quadratic and worst-case O(n²·m²) CPU work before any resolver or AST-based depth or complexity control runs. An unauthenticated remote attacker can submit a shallow, highly compressible GraphQL query that pins a worker process and can saturate a multi-worker service. 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":"none_known"},"has_fix":true,"headline":"GraphQL-core: Denial of service via quadratic complexity in the OverlappingFieldsCanBeMerged validation rule","id":"CVE-2026-75507","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":null,"year":"2026"},"n_packages":4,"n_references":5,"next":{"headline":"GraphQL-core: Denial of service via comment tokens bypassing the parser's max_tokens limit","id":"CVE-2026-75508"},"packages":[{"ecosystem":"PyPI","fixed":["3.2.12"],"introduced":["3.0.0"],"last_affected":[],"package":"graphql-core","purl":null,"source":"GHSA-vj8h-fx38-h3vc"},{"ecosystem":"PyPI","fixed":["3.2.12"],"introduced":["3.0.0"],"last_affected":[],"package":"graphql-core","purl":"pkg:pypi/graphql-core","source":"GHSA-vj8h-fx38-h3vc"},{"ecosystem":"PyPI","fixed":["3.3.0rc1"],"introduced":["3.3.0a1"],"last_affected":[],"package":"graphql-core","purl":null,"source":"GHSA-vj8h-fx38-h3vc"},{"ecosystem":"PyPI","fixed":["3.3.0rc1"],"introduced":["3.3.0a1"],"last_affected":[],"package":"graphql-core","purl":"pkg:pypi/graphql-core","source":"GHSA-vj8h-fx38-h3vc"}],"prev":{"headline":"EspoCRM: Access control bypass in Mass Update letting regular user with Mass Update permission read any attachment","id":"CVE-2026-75505"},"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-23","vendors":["graphql-python"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-75507/"}