sqlparse vulnerabilities — 6 matching vulnerabilities
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.
| Severity | Vulnerability | Package | Ecosystem | Disclosed | Fixed version |
|---|---|---|---|---|---|
| 7.5 high | CVE-2026-59893: sqlparse Denial of Service via Inefficient Regex Handling of Dollar-Quoted SQL Literals |
sqlparse
|
PyPI | 17 Aug 2026 | 0.6.0 |
| 8.7 high | CVE-2026-54284: sqlparse CPU DoS Vulnerability Due to Inefficient Token Grouping |
sqlparse
|
PyPI | 17 Aug 2026 | 0.6.0 |
| 8.7 high | CVE-2026-71491: sqlparse Denial of Service Vulnerability Due to Quadratic Complexity in Group Comments |
sqlparse
|
PyPI | 17 Aug 2026 | 0.6.0 |
| 7.5 high | Duplicate Advisory: Denial of Service in sqlparse |
sqlparse
|
PyPI | 30 Apr 2024 | 0.5.0 |
| 7.5 high | Denial of Service in sqlparse |
sqlparse
|
PyPI | 15 Apr 2024 | 0.5.0 |
| 7.5 high | CVE-2021-32839: Vulnerability in sqlparse package - Regular Expression Denial of Service |
sqlparse
|
PyPI | 10 Sep 2021 | 0.4.2 |
Questions
Searching the database
How do I search for a CVE or a package?
Type a CVE id, package name, ecosystem or keyword into the search field. Results include the severity, the affected package, the ecosystem, the disclosure date and the fixed version.
Can I filter by severity or by whether a fix exists?
Yes. The filters on the left narrow the list to critical, high, medium or low vulnerabilities, to a single ecosystem, and to vulnerabilities that have a fix available or none yet.
What does "No fix published" mean?
No patched version has been released for that vulnerability yet. The vulnerability page still shows the affected range and any workaround that can reduce exposure in the meantime.