VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

sqlparse: vulnerability history, versions and safety

sqlparse is a package in the PyPI ecosystem. Vulert records 18 vulnerabilities for it across 38 releases, from Sep 2021 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
18 vulnerabilities recorded H6 M4 U8
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
12 in the last 12 months

Most recent disclosure 10 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all sqlparse vulnerabilities

Vulert verdict on sqlparse 0.6.0 i

Updated on 23 Oct 2026

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

Package health score 68/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 0.6.0 — unaffected i
  • Vulnerabilities on record 18 over 4 years · 12 in the last year i
  • Latest disclosure 10 Sep 2026 i
  • Highest CVSS 8.7 i
  • With no published fix 0 i
  • Depended on by 18,024 packages i
  • Stars 4,023 i
  • OpenSSF scorecard 5/10 i
  • Last release 2 months ago i
  • Licence non-standard 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 sqlparse, 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.6.0 13 Aug 2026 none non-standard — Details →
0.5.5 19 Dec 2025 H3 M2 U5 non-standard Yes Details →
0.5.4 28 Nov 2025 H3 M2 U5 non-standard Yes Details →
0.5.3 10 Dec 2024 H3 M3 U5 non-standard Yes Details →
0.5.2 14 Nov 2024 H3 M3 U5 non-standard Yes Details →
0.5.1 15 Jul 2024 H3 M3 U5 non-standard Yes Details →
0.5.0 13 Apr 2024 H3 M3 U5 non-standard Yes Details →
0.4.4 18 Apr 2023 H5 M3 U6 non-standard Yes Details →
0.4.3 23 Sep 2022 H5 M4 U7 BSD-3-Clause Yes Details →
0.4.2 10 Sep 2021 H5 M4 U7 BSD-3-Clause Yes Details →
0.4.1 08 Oct 2020 H6 M4 U8 BSD-3-Clause Yes Details →
0.4.0 07 Oct 2020 H6 M4 U8 BSD-3-Clause Yes Details →
0.3.1 29 Feb 2020 H5 M4 U7 non-standard Yes Details →
0.3.0 11 Mar 2019 H5 M4 U7 non-standard Yes Details →
0.2.4 27 Sep 2017 H5 M4 U7 non-standard Yes Details →
0.2.3 02 Mar 2017 H5 M4 U7 non-standard Yes Details →
0.2.2 22 Oct 2016 H5 M4 U7 non-standard Yes Details →
0.2.0 02 Oct 2016 H5 M4 U7 non-standard Yes Details →
0.2.1 02 Oct 2016 H5 M4 U7 non-standard Yes Details →
0.1.19 07 Mar 2016 H5 M4 U7 non-standard Yes Details →
0.1.18 25 Oct 2015 H5 M4 U7 non-standard Yes Details →
0.1.17 24 Oct 2015 H5 M4 U7 non-standard Yes Details →
0.1.16 26 Jul 2015 H5 M4 U7 non-standard Yes Details →
0.1.15 15 Apr 2015 H5 M4 U7 non-standard Yes Details →
0.1.14 30 Nov 2014 H5 M3 U6 non-standard Yes Details →
0.1.13 09 Oct 2014 H5 M3 U6 non-standard Yes Details →
0.1.12 20 Sep 2014 H5 M3 U6 non-standard Yes Details →
0.1.11 07 Feb 2014 H5 M3 U6 non-standard Yes Details →
0.1.10 02 Nov 2013 H5 M3 U6 non-standard Yes Details →
0.1.9 28 Sep 2013 H5 M3 U6 non-standard Yes Details →
0.1.8 29 Jun 2013 H5 M3 U6 non-standard Yes Details →
0.1.5 20 May 2013 H5 M3 U6 non-standard Yes Details →
0.1.3 20 May 2013 H5 M3 U6 non-standard Yes Details →
0.1.2 20 May 2013 H5 M3 U6 non-standard Yes Details →
0.1.1 20 May 2013 H5 M3 U6 non-standard Yes Details →
0.1.0 20 May 2013 H5 M3 U6 non-standard Yes Details →
0.1.7 06 Apr 2013 H5 M3 U6 non-standard Yes Details →
0.1.6 01 Jan 2013 H5 M3 U6 non-standard Yes Details →
0.1.4 20 Apr 2012 H5 M3 U6 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2
  • 2023 2
  • 2024 2
  • 2026 12

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

03 Vulnerabilities

Recorded vulnerabilities for sqlparse

The 5 most severe of 18 vulnerabilities recorded for this package

Search all 18 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2026-71491: sqlparse Denial of Service Vulnerability Due to Quadratic Complexity in Group Comments 8.7 high 0.6.0 17 Aug 2026
CVE-2026-71491: sqlparse Denial of Service Vulnerability Due to Quadratic Complexity in Comment Grouping 8.7 high 0.6.0 19 Aug 2026
CVE-2026-54284: sqlparse CPU DoS Vulnerability Due to Inefficient Token Grouping 8.7 high 0.6.0 19 Aug 2026
CVE-2026-54284: sqlparse CPU DoS Vulnerability Due to Inefficient Token Grouping 8.7 high 0.6.0 17 Aug 2026
CVE-2021-32839: Vulnerability in sqlparse package - Regular Expression Denial of Service 7.5 high 0.4.2 10 Sep 2021

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 sqlparse

Is sqlparse safe to use?

Vulert records 18 vulnerabilities for sqlparse in PyPI: 0 critical, 6 high, 4 medium and 0 low, plus 8 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 sqlparse's Vulert package health score?

Vulert scores sqlparse 68/100, which reads as usable, but worth attention. 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 sqlparse affected?

No. 0.6.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 sqlparse should I use?

0.6.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 sqlparse have?

18 vulnerabilities are recorded for sqlparse in the PyPI ecosystem: 0 critical, 6 high, 4 medium and 0 low, plus 8 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 sqlparse vulnerabilities disclosed?

12 vulnerabilities were recorded for sqlparse in the last 12 months, and the oldest entry in this database dates to 10 Sep 2021. 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 sqlparse 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 sqlparse for upcoming vulnerabilities?

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