# CVE-2026-54284: sqlparse: TokenList.__init__ materializes O(subtree) value per group, causing CPU DoS before depth/token caps trigger

> Attackers can cause CPU exhaustion and denial of service in applications using sqlparse by submitting deeply nested SQL queries.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** CLEANSTART-2026-AA29461, CLEANSTART-2026-TN13603, CLEANSTART-2026-XN67293, DEBIAN-CVE-2026-54284, ECHO-5d2b-9e8c-bdec, GHSA-pwgv-4x5q-6m9f, MINI-7995-62m7-m7f5, MINI-fg4f-mqm3-6h5g, MINI-vvv4-j2vg-23xg, MINI-w3mw-6pcg-vprv, MINI-xc22-28jq-2fpw, PYSEC-2026-3699, ROOT-APP-PYPI-CVE-2026-54284, UBUNTU-CVE-2026-54284

## What is CVE-2026-54284?

CVE-2026-54284 is a high-severity denial of service vulnerability in andialbrecht sqlparse, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, TokenList construction and string conversion in sqlparse/sql.py repeatedly flatten nested token subtrees constructed by group_parenthesis and group_case, causing quadratic CPU consumption through sqlparse.parse(), sqlparse.format(), and sqlparse.split() before depth and token limits terminate processing. This issue is fixed in version 0.6.0.

Weakness: CWE-407 (Inefficient Algorithmic Complexity), CWE-1333 (Inefficient Regular Expression Complexity)

## Which versions are affected by CVE-2026-54284?

3 open source packages ship an affected version, including sqlparse.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sqlparse` | PyPI | All versions | 0.6.0 |
| `sqlparse` | PyPI | All versions | 0.6.0 |
| `sqlparse` | PyPI | All versions | 0.6.0 |

## How do I fix CVE-2026-54284?

Upgrade sqlparse to 0.6.0 or later.

## Is CVE-2026-54284 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54284 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54284 and fix it if it is affected.

What it is: CVE-2026-54284 is a high-severity denial of service vulnerability in andialbrecht sqlparse, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54284 exists.

Affected packages and fixed versions:
- sqlparse (PyPI): affected all versions; fixed in 0.6.0
- sqlparse (PyPI): affected all versions; fixed in 0.6.0
- sqlparse (PyPI): affected all versions; fixed in 0.6.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54284/ (Markdown: https://insights.sbomify.com/CVE-2026-54284/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54284
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54284
- OSV: https://osv.dev/vulnerability/CVE-2026-54284

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54284/
Summaries are generated and may contain mistakes; the official description above is the record.