Vulnerability Database · Debian · sqlparse · Version
sqlparse 0.5.2-1
0.5.2-1 is affected by 4 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 0 High 1 Medium 0 Low 0 Unrated 3
-
Database updated 22/Oct/2026
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.5.2-1 vulnerabilities
4 vulnerabilities cover sqlparse 0.5.2-1. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| High CPU Consumption Vulnerability in sqlparse Package | 7.5 high | No fix published | 17 Aug 2026 |
| High CPU Consumption Vulnerability in sqlparse Package | N/A unrated | No fix published | 17 Aug 2026 |
| SQL Injection Risk in sqlparse Package: CVE-2026-59894 | N/A unrated | No fix published | 17 Aug 2026 |
| High CPU Consumption Vulnerability in sqlparse Package | N/A unrated | No fix published | 17 Aug 2026 |
Looking for another version, or everything Vulert holds for sqlparse?
Questions
About sqlparse 0.5.2-1
Is sqlparse 0.5.2-1 vulnerable?
Yes. 4 vulnerabilities in the Vulert database cover sqlparse 0.5.2-1: 0 critical, 1 high, 0 medium and 0 low, plus 3 not yet rated. Each entry above names the fixed version to move to.
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.