Advisories
This weekExploitable · Confirmed

graphql-core: GraphQL-core: Denial of service via comment tokens bypassing the parser's max_tokens limit

There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.

Does it affect what I run?

graphql-core (PyPI)

Checked in your browser. The version you type is not sent anywhere.

Who is affected

  • graphql-core (PyPI): from 3.2.3, before 3.2.12
  • graphql-core (PyPI): from 3.3.0a3, before 3.3.0rc1

The fix

  • graphql-core (PyPI) fixed in 3.2.12

    pip
    python -m pip install graphql-core==3.2.12
    uv
    uv add graphql-core==3.2.12
    poetry
    poetry add graphql-core@3.2.12
    Check what is installed
    python -m pip show graphql-core
    Paste into Cursor, Lovable or Claude Code
    Upgrade the PyPI dependency graphql-core to 3.2.12 or the nearest later release, to fix CVE-2026-75508. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • graphql-core (PyPI) fixed in 3.3.0rc1

    pip
    python -m pip install graphql-core==3.3.0rc1
    uv
    uv add graphql-core==3.3.0rc1
    poetry
    poetry add graphql-core@3.3.0rc1
    Check what is installed
    python -m pip show graphql-core
    Paste into Cursor, Lovable or Claude Code
    Upgrade the PyPI dependency graphql-core to 3.3.0rc1 or the nearest later release, to fix CVE-2026-75508. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.

Fix commands generated from the advisory's versions. No model wrote them.

In plain words

Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.

Evidence

Timeline

  1. First published here, as "For your digest".
  2. Level changed from "For your digest" to "This week".
  3. Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))