Vulnerability Database · PyPI · Package report

strawberry-graphql: vulnerability history, versions and safety

strawberry-graphql is a package in the PyPI ecosystem. Vulert records 19 vulnerabilities for it across 120 releases, from Sep 2024 to 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
19 vulnerabilities recorded C1 H3 M3 L3 U9
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
16 in the last 12 months

Most recent disclosure 15 Oct 2026.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in PyPI →

Vulert verdict on strawberry-graphql 0.336.2 i

Updated on 23 Oct 2026

Careful: 0.336.2 was published with malicious code in it, not just a bug. Do not install it.

Package health score 15/100
  • Security Malicious code published
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

The current release contains malicious code, which caps this score.

What to do: Do not resolve 0.336.2 as-is. Check whether you already run an affected release and pin a version the maintainers have re-published. Check what you run: Vulert alerts you when a safe version is published. Monitor it with Vulert →

  • Current release 0.336.2 — affected i
  • Vulnerabilities on record 19 over 2 years · 16 in the last year i
  • Latest disclosure 15 Oct 2026 i
  • Highest CVSS 8.0 i
  • With no published fix 1 i
  • Malicious packages 1 i
  • Depended on by 209 packages i
  • Stars 4,726 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 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 strawberry-graphql, 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
0.336.2 20 Oct 2026 C1 U1 malicious MIT No Details →
0.336.1 20 Oct 2026 C1 U1 malicious MIT No Details →
0.336.0 17 Oct 2026 C1 U1 malicious MIT No Details →
0.335.0 14 Oct 2026 C1 U1 malicious MIT No Details →
0.334.4 13 Oct 2026 C1 U1 malicious MIT No Details →
0.334.3 12 Oct 2026 C1 U1 malicious MIT No Details →
0.334.2 12 Oct 2026 C1 U1 malicious MIT No Details →
0.334.1 11 Oct 2026 C1 U1 malicious MIT No Details →
0.334.0 11 Oct 2026 C1 U1 malicious MIT No Details →
0.333.0 10 Oct 2026 C1 U1 malicious MIT No Details →
0.332.1 09 Oct 2026 C1 U1 malicious MIT No Details →
0.332.0 06 Oct 2026 C1 U1 malicious MIT No Details →
0.331.6 05 Oct 2026 C1 U1 malicious MIT No Details →
0.331.5 05 Oct 2026 C1 U1 malicious MIT No Details →
0.331.4 05 Oct 2026 C1 U1 malicious MIT No Details →
0.331.3 05 Oct 2026 C1 U1 malicious MIT No Details →
0.331.2 05 Oct 2026 C1 U1 malicious MIT No Details →
0.331.1 04 Oct 2026 C1 U1 malicious MIT No Details →
0.331.0 04 Oct 2026 C1 U1 malicious MIT No Details →
0.330.3 04 Oct 2026 C1 U1 malicious MIT No Details →
0.330.2 03 Oct 2026 C1 U1 malicious MIT No Details →
0.330.1 03 Oct 2026 C1 U1 malicious MIT No Details →
0.330.0 03 Oct 2026 C1 U1 malicious MIT No Details →
0.329.0 02 Oct 2026 C1 U1 malicious MIT No Details →
0.328.3 02 Oct 2026 C1 U1 malicious MIT No Details →
0.328.2 02 Oct 2026 C1 U1 malicious MIT No Details →
0.328.1 02 Oct 2026 C1 U1 malicious MIT No Details →
0.328.0 30 Sep 2026 C1 U1 malicious MIT No Details →
0.327.7 07 Sep 2026 C1 U1 malicious MIT No Details →
0.327.6 07 Sep 2026 C1 U1 malicious MIT No Details →
0.327.5 07 Sep 2026 C1 U1 malicious MIT No Details →
0.327.4 06 Sep 2026 C1 U1 malicious MIT No Details →
0.327.3 05 Sep 2026 C1 U1 malicious MIT No Details →
0.327.2 03 Sep 2026 C1 U1 malicious MIT No Details →
0.327.1 01 Sep 2026 L1 U1 MIT Yes Details →
0.327.0 31 Aug 2026 L1 U1 MIT Yes Details →
0.326.1 31 Aug 2026 L1 U1 MIT Yes Details →
0.326.0 31 Aug 2026 H1 L1 U2 MIT Yes Details →
0.325.0 30 Aug 2026 H1 L1 U2 MIT Yes Details →
0.324.5 30 Aug 2026 H1 L1 U2 MIT Yes Details →
0.324.4 29 Aug 2026 H1 L1 U2 MIT Yes Details →
0.324.3 29 Aug 2026 H1 L1 U2 MIT Yes Details →
0.324.2 28 Aug 2026 H1 L1 U2 MIT Yes Details →
0.324.1 28 Aug 2026 H1 L1 U2 MIT Yes Details →
0.324.0 10 Aug 2026 H1 L1 U2 MIT Yes Details →
0.323.2 23 Jul 2026 H1 L1 U2 MIT Yes Details →
0.323.1 22 Jul 2026 H1 L1 U2 MIT Yes Details →
0.323.0 21 Jul 2026 H1 L1 U2 MIT Yes Details →
0.322.2 20 Jul 2026 H1 L1 U2 MIT Yes Details →
0.322.1 20 Jul 2026 H1 L1 U2 MIT Yes Details →
0.322.0 18 Jul 2026 H1 L1 U2 MIT Yes Details →
0.321.1 17 Jul 2026 H1 L1 U2 MIT Yes Details →
0.321.0 13 Jul 2026 H1 L1 U2 MIT Yes Details →
0.320.4 09 Jul 2026 H1 L1 U2 MIT Yes Details →
0.320.3 07 Jul 2026 H1 L1 U2 MIT Yes Details →
0.320.2 06 Jul 2026 H1 L1 U2 MIT Yes Details →
0.320.1 02 Jul 2026 H1 L1 U2 MIT Yes Details →
0.320.0 27 Jun 2026 H1 L1 U2 MIT Yes Details →
0.319.0 21 Jun 2026 H1 L1 U2 MIT Yes Details →
0.318.1 20 Jun 2026 H1 L1 U2 MIT Yes Details →
0.318.0 19 Jun 2026 H1 L1 U2 MIT Yes Details →
0.317.2 17 Jun 2026 H1 L1 U2 MIT Yes Details →
0.317.1 17 Jun 2026 H1 L1 U2 MIT Yes Details →
0.317.0 17 Jun 2026 H1 L1 U2 MIT Yes Details →
0.316.0 19 May 2026 H1 L1 U2 MIT Yes Details →
0.315.7 19 May 2026 H1 L1 U2 MIT Yes Details →
0.315.6 19 May 2026 C1 H1 M2 L1 U4 malicious MIT No Details →
0.315.5 14 May 2026 H1 M2 L1 U4 MIT Yes Details →
0.315.4 12 May 2026 H1 M2 L1 U4 MIT Yes Details →
0.315.3 29 Apr 2026 H1 M2 L2 U5 MIT Yes Details →
0.315.2 26 Apr 2026 H1 M2 L2 U5 MIT Yes Details →
0.315.1 25 Apr 2026 H1 M2 L2 U5 MIT Yes Details →
0.315.0 24 Apr 2026 H1 M2 L2 U5 MIT Yes Details →
0.314.3 08 Apr 2026 H1 M2 L2 U5 MIT Yes Details →
0.314.2 08 Apr 2026 H1 M2 L2 U5 MIT Yes Details →
0.314.1 08 Apr 2026 H1 M2 L2 U5 MIT Yes Details →
0.314.0 07 Apr 2026 H1 M2 L2 U5 MIT Yes Details →
0.313.0 06 Apr 2026 H1 M2 L2 U5 MIT Yes Details →
0.312.4 05 Apr 2026 H1 M2 L2 U5 MIT Yes Details →
0.312.3 04 Apr 2026 H1 M2 L2 U5 MIT Yes Details →
0.312.2 25 Mar 2026 H3 M2 L1 U6 MIT Yes Details →
0.312.1 25 Mar 2026 H3 M2 L1 U6 MIT Yes Details →
0.312.0 21 Mar 2026 H3 M2 L1 U6 MIT Yes Details →
0.311.3 16 Mar 2026 H3 M2 L1 U6 MIT Yes Details →
0.311.2 16 Mar 2026 H3 M2 L1 U6 MIT Yes Details →
0.311.1 10 Mar 2026 H3 M2 L1 U6 MIT Yes Details →
0.311.0 08 Mar 2026 H3 M2 L1 U6 MIT Yes Details →
0.310.2 08 Mar 2026 H3 M2 L1 U6 MIT Yes Details →
0.310.1 08 Mar 2026 H3 M2 L1 U6 MIT Yes Details →
0.310.0 08 Mar 2026 H3 M2 L1 U6 MIT Yes Details →
0.309.0 08 Mar 2026 H3 M2 L1 U6 MIT Yes Details →
0.308.3 04 Mar 2026 H3 M2 L1 U6 MIT Yes Details →
0.308.2 03 Mar 2026 H3 M2 L1 U6 MIT Yes Details →
0.308.1 03 Mar 2026 H3 M2 L1 U6 MIT Yes Details →
0.308.0 03 Mar 2026 H3 M2 L1 U6 MIT Yes Details →
0.307.1 24 Feb 2026 H3 M2 L1 U6 MIT Yes Details →
0.307.0 24 Feb 2026 H3 M2 L1 U6 MIT Yes Details →
0.306.0 23 Feb 2026 H3 M2 L1 U6 MIT Yes Details →
0.305.0 22 Feb 2026 H3 M2 L1 U6 MIT Yes Details →
0.304.0 22 Feb 2026 H3 M2 L1 U6 MIT Yes Details →
0.303.1 22 Feb 2026 H3 M2 L1 U6 — Yes Details →
0.303.0 22 Feb 2026 H3 M2 L1 U6 — Yes Details →
0.302.0 22 Feb 2026 H3 M2 L1 U6 — Yes Details →
0.301.0 22 Feb 2026 H3 M2 L1 U6 — Yes Details →
0.300.0 21 Feb 2026 H3 M2 L1 U6 — Yes Details →
0.299.0 20 Feb 2026 H3 M2 L1 U6 — Yes Details →
0.298.1 20 Feb 2026 H3 M2 L1 U6 — Yes Details →
0.298.0 20 Feb 2026 H3 M2 L1 U6 — Yes Details →
0.297.0 19 Feb 2026 H3 M2 L1 U6 — Yes Details →
0.296.2 19 Feb 2026 H3 M2 L1 U6 — Yes Details →
0.291.2.dev1771437961 18 Feb 2026 H3 M2 L1 U6 — Yes Details →
0.296.1 17 Feb 2026 H3 M2 L1 U6 — Yes Details →
0.296.0 17 Feb 2026 H3 M2 L1 U6 — Yes Details →
0.295.0 17 Feb 2026 H3 M2 L1 U6 — Yes Details →
0.294.0 17 Feb 2026 H3 M2 L1 U6 — Yes Details →
0.293.0 16 Feb 2026 H3 M2 L1 U6 — Yes Details →
0.292.0 16 Feb 2026 H3 M2 L1 U6 — Yes Details →
0.291.2.dev1770456508 07 Feb 2026 H3 M2 L1 U6 — Yes Details →
0.291.3 07 Feb 2026 H3 M2 L1 U6 — Yes Details →
0.291.2 06 Feb 2026 H3 M2 L1 U6 — Yes Details →

The newest 120 of 1,142 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2
  • 2025 1
  • 2026 16

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

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 strawberry-graphql

Is strawberry-graphql safe to use?

Vulert records 19 vulnerabilities for strawberry-graphql in PyPI: 1 critical, 3 high, 3 medium and 3 low, plus 9 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate. 1 are malicious-package vulnerabilities: the published package itself contained hostile code, not only a bug.

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

Vulert scores strawberry-graphql 15/100, which reads as critical. 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). The current release contains malicious code, which caps this score.

Is the latest version of strawberry-graphql affected?

Yes. 0.336.2, the version you would install today, has 2 known vulnerabilities, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does strawberry-graphql have?

19 vulnerabilities are recorded for strawberry-graphql in the PyPI ecosystem: 1 critical, 3 high, 3 medium and 3 low, plus 9 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new strawberry-graphql vulnerabilities disclosed?

16 vulnerabilities were recorded for strawberry-graphql in the last 12 months, and the oldest entry in this database dates to 25 Sep 2024. 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 strawberry-graphql 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.

What does a malicious-package vulnerability mean?

It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.

How do I monitor strawberry-graphql for upcoming vulnerabilities?

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