CVE-2026-54284
Quadratic-time CPU DoS in sqlparse (<0.6.0) via nested token parsing
Is CVE-2026-54284 being exploited?
Not confirmed. CVE-2026-54284 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-54284?
CVE-2026-54284 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-54284?
Yes. A fix has been recorded for CVE-2026-54284. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-54284 affect?
CVE-2026-54284 affects sqlparse < 0.6.0, Python applications using sqlparse (parse/format/split). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-54284?
Upgrade sqlparse to >=0.6.0; validate/rate-limit untrusted SQL input
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted SQL input causes quadratic CPU growth in sqlparse.parse/format/split, enabling denial-of-service of apps that parse attacker-controlled SQL.
Patch when possible
- affected< 0.6.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.