VulertSecurity VulertSecurity

Vulnerability Database · PyPI · sqlparse · Version

sqlparse 0.2.4

0.2.4 is affected by 16 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 0.6.0.

Critical 0 High 9 Medium 6 Low 0 Unrated 1

All sqlparse versions & vulnerabilities → Source repository Search the database for this package →
Released 27 Sep 2017 Licence non-standard Also known from other sources 15 Newer releases 39 Database updated 23/Oct/2026

Release and licence data published by PyPI. 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 Vulnerabilities affecting this version

sqlparse 0.2.4 vulnerabilities

16 vulnerabilities cover sqlparse 0.2.4. Scroll the table for all of them, or open the full list in the database.

Vulnerability Severity Fixed version Disclosed
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-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-59893: sqlparse Denial of Service Vulnerability Due to Inefficient Regex Handling 7.5 high 0.6.0 19 Aug 2026
CVE-2026-59893: sqlparse Denial of Service via Inefficient Regex Handling of Dollar-Quoted SQL Literals 7.5 high 0.6.0 17 Aug 2026
CVE-2024-4340: sqlparse Denial of Service via Heavily Nested List Parsing 7.5 high 0.5.0 07 Jul 2026
Duplicate Advisory: Denial of Service in sqlparse 7.5 high 0.5.0 30 Apr 2024
Denial of Service in sqlparse 7.5 high 0.5.0 15 Apr 2024
Denial of Service Vulnerability in sqlparse: Formatting Long Tuples 6.9 medium 0.5.4 13 Feb 2026
CVE-2026-59894: sqlparse Package Vulnerability Allows SQL String Breakout Through Unescaped Backslashes 6.2 medium 0.6.0 19 Aug 2026
CVE-2026-59894: sqlparse Vulnerability Allows SQL String Breakout Through Unescaped Backslashes 6.2 medium 0.6.0 17 Aug 2026
CVE-2023-30608: Vulnerability in sqlparse - Regular Expression Denial of Service 5.5 medium 0.4.4 21 Apr 2023
CVE-2026-84305: sqlparse Tuple List Reindentation Causes CPU Exhaustion Vulnerability 5.1 medium 0.6.0 10 Sep 2026
CVE-2026-84305: sqlparse Tuple List Reindentation Causes CPU Resource Exhaustion 5.1 medium 0.6.0 01 Sep 2026
CVE-2023-30608: sqlparse Regular Expression Denial of Service Vulnerability N/A unrated c457abd5f097dd13fb21543381e7cfafe7d31cfb 18 Apr 2023

Looking for another version, or everything Vulert holds for sqlparse?

All versions → Full vulnerability list →

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 0.2.4

Is sqlparse 0.2.4 vulnerable?

Yes. 16 vulnerabilities in the Vulert database cover sqlparse 0.2.4: 0 critical, 9 high, 6 medium and 0 low, plus 1 not yet rated. The upgrade Vulert recommends is 0.6.0, and each entry above names the fixed version to move to.

Which version of sqlparse should I use instead of 0.2.4?

0.6.0 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is 0.2.4 the latest release of sqlparse?

No. 0.2.4 was published 27 Sep 2017, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

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.