# GHSA-27jp-wm6q-gp25: sqlparse: formatting list of tuples leads to denial of service

> An attacker can cause a denial of service by providing a long list of tuples to the sqlparse library for formatting.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Feb 2026

## What is GHSA-27jp-wm6q-gp25?

GHSA-27jp-wm6q-gp25 is a denial of service vulnerability in sqlparse, published on 13 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### Summary
The below gist hangs while attempting to format a long list of tuples.

This was found while [drafting a regression test for Dja
ngo 5.2's composite primary key feature](https://code.djangoproject.com/ticket/36416#comment:3), which allows querying composite fields with tuples.

###

## Which versions are affected by GHSA-27jp-wm6q-gp25?

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


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

## How do I fix GHSA-27jp-wm6q-gp25?

Upgrade sqlparse to 0.5.4 or later.

## Is GHSA-27jp-wm6q-gp25 being exploited?

There is no known exploitation of GHSA-27jp-wm6q-gp25 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-27jp-wm6q-gp25 and fix it if it is affected.

What it is: GHSA-27jp-wm6q-gp25 is a denial of service vulnerability in sqlparse, published on 13 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-27jp-wm6q-gp25 in the wild and no public exploit code.

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

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/GHSA-27jp-wm6q-gp25/ (Markdown: https://insights.sbomify.com/GHSA-27jp-wm6q-gp25/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-27jp-wm6q-gp25

---
From sbomify Insights: https://insights.sbomify.com/GHSA-27jp-wm6q-gp25/
Summaries are generated and may contain mistakes; the official description above is the record.