VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

quart: vulnerability history, versions and safety

quart is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 65 releases, from Jul 2026 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
2 vulnerabilities recorded H1 U1
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 05 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all quart vulnerabilities

Vulert verdict on quart 0.23.1 i

Updated on 23 Oct 2026

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

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 0.23.1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 05 Oct 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 204 packages i
  • Stars 3,678 i
  • Last release 1 month ago 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 quart, 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.23.1 29 Aug 2026 none MIT — Details →
0.23.0 29 Aug 2026 H1 MIT Yes Details →
0.22.0 19 Aug 2026 none MIT — Details →
0.21.0 23 Jul 2026 none MIT — Details →
0.20.0 23 Dec 2024 none MIT — Details →
0.19.9 14 Nov 2024 U1 MIT Yes Details →
0.19.8 25 Oct 2024 U1 MIT Yes Details →
0.19.7 25 Oct 2024 U1 MIT Yes Details →
0.19.6 19 May 2024 U1 MIT Yes Details →
0.19.5 01 Apr 2024 U1 MIT Yes Details →
0.19.4 19 Nov 2023 U1 MIT Yes Details →
0.19.3 04 Oct 2023 U1 MIT Yes Details →
0.19.2 01 Oct 2023 U1 MIT Yes Details →
0.19.1 30 Sep 2023 U1 MIT Yes Details →
0.19.0 30 Sep 2023 U1 MIT Yes Details →
0.18.4 09 Apr 2023 U1 MIT Yes Details →
0.18.3 08 Oct 2022 U1 MIT Yes Details →
0.18.2 04 Oct 2022 U1 MIT Yes Details →
0.18.1 03 Oct 2022 U1 MIT Yes Details →
0.18.0 23 Jul 2022 U1 MIT Yes Details →
0.17.0 26 Mar 2022 U1 MIT Yes Details →
0.16.3 02 Feb 2022 U1 MIT Yes Details →
0.16.2 14 Dec 2021 U1 MIT Yes Details →
0.16.1 17 Nov 2021 U1 MIT Yes Details →
0.16.0 09 Nov 2021 U1 MIT Yes Details →
0.15.1 24 May 2021 U1 MIT Yes Details →
0.15.0 11 May 2021 U1 MIT Yes Details →
0.14.1 13 Dec 2020 U1 MIT Yes Details →
0.14.0 05 Dec 2020 U1 MIT Yes Details →
0.13.1 09 Sep 2020 U1 MIT Yes Details →
0.13.0 14 Jul 2020 U1 MIT Yes Details →
0.12.0 21 May 2020 U1 MIT Yes Details →
0.11.5 31 Mar 2020 U1 MIT Yes Details →
0.11.4 29 Mar 2020 U1 MIT Yes Details →
0.11.3 26 Feb 2020 U1 MIT Yes Details →
0.11.2 10 Feb 2020 U1 MIT Yes Details →
0.11.1 09 Feb 2020 U1 MIT Yes Details →
0.11.0 08 Feb 2020 U1 MIT Yes Details →
0.6.15 17 Oct 2019 U1 MIT Yes Details →
0.10.0 30 Aug 2019 U1 MIT Yes Details →
0.6.14 30 Aug 2019 U1 MIT Yes Details →
0.9.1 12 May 2019 U1 MIT Yes Details →
0.9.0 22 Apr 2019 U1 MIT Yes Details →
0.6.13 22 Apr 2019 U1 MIT Yes Details →
0.8.1 09 Feb 2019 U1 MIT Yes Details →
0.8.0 29 Jan 2019 U1 MIT Yes Details →
0.6.12 29 Jan 2019 U1 MIT Yes Details →
0.7.2 03 Jan 2019 U1 MIT Yes Details →
0.7.1 18 Dec 2018 U1 MIT Yes Details →
0.7.0 16 Dec 2018 U1 MIT Yes Details →
0.6.11 09 Dec 2018 U1 MIT Yes Details →
0.6.10 12 Nov 2018 U1 MIT Yes Details →
0.6.9 10 Nov 2018 U1 MIT Yes Details →
0.6.8 21 Oct 2018 U1 MIT Yes Details →
0.6.7 23 Sep 2018 U1 MIT Yes Details →
0.6.6 27 Aug 2018 U1 MIT Yes Details →
0.6.5 05 Aug 2018 U1 MIT Yes Details →
0.6.4 15 Jul 2018 U1 MIT Yes Details →
0.6.3 05 Jul 2018 U1 MIT Yes Details →
0.6.2 24 Jun 2018 U1 MIT Yes Details →
0.6.1 18 Jun 2018 U1 MIT Yes Details →
0.6.0 11 Jun 2018 U1 MIT Yes Details →
0.5.0 14 Apr 2018 U1 MIT Yes Details →
0.4.1 27 Jan 2018 U1 MIT Yes Details →
0.4.0 14 Jan 2018 U1 MIT Yes Details →
0.3.1 25 Oct 2017 U1 MIT Yes Details →
0.3.0 10 Oct 2017 U1 MIT Yes Details →
0.2.0 22 Jul 2017 U1 MIT Yes Details →
0.1.0 21 May 2017 U1 MIT Yes Details →

All 69 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 quart

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-49767: Quart Package Resource Exhaustion Vulnerability in Werkzeug 7.5 high 0.20.0 07 Jul 2026
Sensitive Data Exposure in Quart 0.23.0: Raw Request Body Leaked to stdout 7.5 high 0.23.1 05 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 quart

Is quart safe to use?

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

What is quart's Vulert package health score?

Vulert scores quart 84/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 quart affected?

No. 0.23.1, 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 quart should I use?

0.23.1 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 quart have?

2 vulnerabilities are recorded for quart in the PyPI ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 1 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 quart vulnerabilities disclosed?

2 vulnerabilities were recorded for quart in the last 12 months, and the oldest entry in this database dates to 07 Jul 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 quart 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 quart for upcoming vulnerabilities?

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