# CVE-2026-59893: sqlparse: Inefficient Regex Handling of Dollar-Quoted SQL Literals Leads to ReDoS (Denial of Service)

> An attacker can cause denial of service via quadratic CPU consumption in the sqlparse library by submitting crafted SQL literals.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **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-JT70619, CLEANSTART-2026-QP37899, CLEANSTART-2026-VD54989, DEBIAN-CVE-2026-59893, ECHO-1e44-b57b-9d8b, GHSA-prg7-hcfm-mfcr, MINI-7c4q-2x7r-m2wg, MINI-99xc-mcp5-c3mj, MINI-jqp7-8mf4-m26f, MINI-v2gp-qhrr-37vf, MINI-x83x-m3j8-9q33, OESA-2026-3547, PYSEC-2026-3698, UBUNTU-CVE-2026-59893

## What is CVE-2026-59893?

CVE-2026-59893 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, SQL_REGEX in sqlparse/keywords.py and the per-position loop in sqlparse/lexer.py repeatedly scan unmatched dollar-quoted literal and multiline-comment delimiters, causing quadratic CPU consumption through sqlparse.parse(), sqlparse.format(), and sqlparse.split(). This issue is fixed in version 0.6.0.

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

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

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-59893?

Upgrade sqlparse to 0.6.0 or later.

## Is CVE-2026-59893 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59893 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-59893 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-59893/ (Markdown: https://insights.sbomify.com/CVE-2026-59893/index.md)
```

## Sources

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

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