VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

graphql-core: vulnerability history, versions and safety

graphql-core is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 35 releases, first recorded in Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 22 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all graphql-core vulnerabilities

Vulert verdict on graphql-core 3.3.0 i

Updated on 23 Oct 2026

Good news: 3.3.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

What to do: Stay on 3.3.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.3.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 3.3.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 22 Oct 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 1,147 packages i
  • Stars 532 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for graphql-core, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.3.0 27 Sep 2026 none MIT — Details →
3.2.13 27 Sep 2026 none MIT — Details →
3.3.0rc1 27 Aug 2026 none MIT — Details →
3.2.12 27 Aug 2026 none MIT — Details →
3.3.0rc0 19 Jun 2026 none MIT — Details →
3.3.0b2 14 Jun 2026 none MIT — Details →
3.3.0b1 13 Jun 2026 none MIT — Details →
3.3.0b0 11 Jun 2026 none MIT — Details →
3.3.0a14 07 Jun 2026 none MIT — Details →
3.3.0a13 07 Jun 2026 none MIT — Details →
3.2.11 05 Jun 2026 H2 MIT Yes Details →
3.2.10 05 Jun 2026 H2 MIT Yes Details →
3.2.9 04 Jun 2026 H2 MIT Yes Details →
3.2.8 05 Mar 2026 H2 MIT Yes Details →
3.3.0a12 05 Mar 2026 none MIT — Details →
3.2.7 01 Nov 2025 H2 MIT Yes Details →
3.3.0a11 01 Nov 2025 none MIT — Details →
3.3.0a10 28 Sep 2025 none MIT — Details →
3.3.0a9 18 Jun 2025 none MIT — Details →
3.3.0a8 24 May 2025 none MIT — Details →
3.3.0a7 26 Jan 2025 none MIT — Details →
3.2.6 26 Jan 2025 H2 MIT Yes Details →
3.2.5 13 Oct 2024 H2 MIT Yes Details →
3.2.4 04 Sep 2024 H2 MIT Yes Details →
3.3.0a6 11 Aug 2024 none MIT — Details →
3.3.0a5 14 Apr 2024 none MIT — Details →
3.3.0a4 17 Feb 2024 none MIT — Details →
3.3.0a3 04 Jun 2023 none MIT — Details →
3.3.0a2 03 Nov 2022 none MIT — Details →
3.3.0a1 24 Sep 2022 none MIT — Details →
3.2.3 23 Sep 2022 H2 MIT Yes Details →
3.2.2 22 Sep 2022 H1 MIT Yes Details →
3.2.1 10 Apr 2022 H1 MIT Yes Details →
3.2.0 15 Jan 2022 H1 MIT Yes Details →
3.2.0rc5 15 Jan 2022 H1 MIT Yes Details →
3.2.0rc4 29 Dec 2021 H1 MIT Yes Details →
3.0.6 29 Dec 2021 H1 MIT Yes Details →
3.2.0rc3 12 Dec 2021 H1 MIT Yes Details →
3.1.7 12 Dec 2021 H1 MIT Yes Details →
3.2.0rc2 30 Sep 2021 H1 MIT Yes Details →
3.2.0rc1 29 Sep 2021 H1 MIT Yes Details →
3.1.6 20 Aug 2021 H1 MIT Yes Details →
3.1.5 10 May 2021 H1 MIT Yes Details →
3.1.4 08 Apr 2021 H1 MIT Yes Details →
3.1.3 08 Feb 2021 H1 MIT Yes Details →
3.1.2 05 Jul 2020 H1 MIT Yes Details →
3.0.5 18 May 2020 H1 MIT Yes Details →
3.1.1 18 May 2020 H1 MIT Yes Details →
2.3.2 12 May 2020 none MIT — Details →
3.1.0 03 Apr 2020 H1 MIT Yes Details →
3.0.4 03 Apr 2020 H1 MIT Yes Details →
3.1.0b2 21 Mar 2020 H1 MIT Yes Details →
3.1.0b1 04 Mar 2020 H1 MIT Yes Details →
3.1.0b0 10 Feb 2020 H1 MIT Yes Details →
3.0.3 02 Feb 2020 H1 MIT Yes Details →
3.0.2 26 Jan 2020 H1 MIT Yes Details →
2.3.1 24 Jan 2020 none MIT — Details →
2.3.0 23 Jan 2020 none MIT — Details →
3.0.1 06 Dec 2019 H1 MIT Yes Details →
3.0.0 30 Nov 2019 H1 MIT Yes Details →
3.0.0b1 26 Sep 2019 none MIT — Details →
3.0.0b0 14 Sep 2019 none MIT — Details →
3.0.0a2 02 Aug 2019 none MIT — Details →
3.0.0a1 28 Jul 2019 none MIT — Details →
2.2.1 18 Jul 2019 none MIT — Details →
3.0.0a0 14 Jul 2019 none MIT — Details →
2.2.0 07 Jun 2019 none MIT — Details →
2.1.0 19 Jul 2018 none MIT — Details →
2.1.0rc3 05 Jul 2018 none MIT — Details →
2.1.0rc2 13 Jun 2018 none MIT — Details →
2.1.0rc1 05 Jun 2018 none MIT — Details →
2.1.0rc0 05 Jun 2018 none MIT — Details →
2.0.0 25 Oct 2017 none MIT — Details →
2.0.0.dev20171009101843 09 Oct 2017 none MIT — Details →
2.0.0.dev20170801051721 01 Aug 2017 none MIT — Details →
2.0.0.dev20170801041408 01 Aug 2017 none MIT — Details →
1.2.0.dev20170724044604 24 Jul 2017 none MIT — Details →
1.1.0 19 Apr 2017 none MIT — Details →
1.0.1 15 Nov 2016 none MIT — Details →
1.0.0 26 Sep 2016 none MIT — Details →
1.0.0.dev20160920065529 20 Sep 2016 none MIT — Details →
1.0.0.dev20160909040033 09 Sep 2016 none MIT — Details →
1.0.0.dev20160909030348 09 Sep 2016 none MIT — Details →
1.0.0.dev20160823054952 23 Aug 2016 none MIT — Details →
1.0.0.dev20160822075425 22 Aug 2016 none MIT — Details →
1.0.0.dev20160814231515 14 Aug 2016 none MIT — Details →
0.5.3 21 Jun 2016 none MIT — Details →
0.5.2 01 Jun 2016 none MIT — Details →
0.5.1 18 May 2016 none MIT — Details →
0.5.0 12 May 2016 none MIT — Details →
0.5.0b3 12 May 2016 none MIT — Details →
0.5.0b2 12 May 2016 none MIT — Details →
0.5.0b1 12 May 2016 none MIT — Details →
0.4.18 19 Apr 2016 none MIT — Details →
0.4.17 19 Apr 2016 none MIT — Details →
0.4.16 19 Apr 2016 none MIT — Details →
0.4.15 18 Apr 2016 none MIT — Details →
0.4.14 16 Apr 2016 none MIT — Details →
0.4.13 14 Apr 2016 none MIT — Details →
0.4.12.1 01 Feb 2016 none MIT — Details →
0.4.12 20 Nov 2015 none — — Details →
0.4.11 19 Nov 2015 none — — Details →
0.4.9 17 Nov 2015 none — — Details →
0.4.7b2 13 Nov 2015 none — — Details →
0.4.7b1 26 Oct 2015 none — — Details →
0.4.7b0 16 Oct 2015 none — — Details →
0.1.0a4 14 Oct 2015 none — — Details →
0.1.0a3 10 Oct 2015 none — — Details →
0.1.0a2 08 Oct 2015 none — — Details →
0.1.0a1 07 Oct 2015 none — — Details →
0.1.0a0 06 Oct 2015 none — — Details →

All 111 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for graphql-core

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-75508: graphql-core token limit bypass enables memory-exhaustion denial of service 7.5 high 3.2.12 22 Oct 2026
CVE-2026-75507: graphql-core validation rule enables denial of service 7.5 high 3.2.12 22 Oct 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About graphql-core

Is graphql-core safe to use?

Vulert records 2 vulnerabilities for graphql-core in PyPI: 0 critical, 2 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is graphql-core's Vulert package health score?

Vulert scores graphql-core 78/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of graphql-core affected?

No. 3.3.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of graphql-core should I use?

3.3.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does graphql-core have?

2 vulnerabilities are recorded for graphql-core in the PyPI ecosystem: 0 critical, 2 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new graphql-core vulnerabilities disclosed?

2 vulnerabilities were recorded for graphql-core in the last 12 months, and the oldest entry in this database dates to 22 Oct 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of graphql-core are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor graphql-core for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the graphql-core version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.