Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-cfqr-cjx5-5jcm

sqlparse: Reindentation of tuple lists causes near-cap quadratic CPU consumption

CVSS 5.1 MediumEPSS 0.0019 · 8th percentile

Published by the GitHub Advisory Database at 1 Sept 2026, 21:20 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
sqlparsePyPI<0.6.00.6.0
Identifiers
GHSA-cfqr-cjx5-5jcm · CVE-2026-84305 · PYSEC-2026-3923
Weakness (CWE)
CWE-407
Tags
Published
1 Sept 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

sqlparse versions before 0.6.0 are vulnerable to a CPU exhaustion issue when SQL is formatted with reindentation enabled (for example via sqlparse.format with reindent=True or the sqlformat --reindent CLI option). An attacker who can supply SQL to that opt-in formatting path can send a crafted, roughly 16 KB parenthesized tuple list that causes multi-second CPU consumption per call, which can delay requests or starve workers. Upgrade to sqlparse 0.6.0 or later. The source gives no other workaround beyond avoiding reindentation of untrusted input.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.1 Medium 4.0 CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0019, the 8th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:10 UTC First seen by agentprime
  2. 31 Oct 2026, 14:10 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.