Skip to content
Fencer Vulns
medium 5.1

CVE-2026-84305 json

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

published 2026-09-01 2 mo ago modified 2026-09-10 1 mo ago also GHSA-cfqr-cjx5-5jcm , PYSEC-2026-3923 , EUVD-2026-69421

cvss
5.1
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 8%
public exploits
0
none known

Summary

sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, sqlparse.format(sql, reindent=True) and sqlformat --reindent route attacker-controlled parenthesized tuple lists through ReindentFilter._get_offset() in sqlparse/filters/reindent.py, where _flatten_up_to_token() repeatedly rebuilds and joins the statement prefix. Thousands of offset calculations walk an expanding token tree, producing quadratic CPU consumption for inputs that remain below MAX_GROUPING_TOKENS and causing request delays, reduced throughput, or worker starvation. This issue is fixed in version 0.6.0.

Patch / fix

  • pypi sqlparse 0.6.0
  • python-sqlparse SLE Module for Python 3 15 SP7, SLE Module for Public Cloud 15 SP6 0.4.4-150600.3.12.1
  • python-sqlparse SLE Module for Public Cloud 15 SP5, SLE Module for Public Cloud 15 SP4 0.4.4-150400.6.19.1
  • python-sqlparse SLES for SAP applications 16.0, SLES 16.0 0.5.3-160000.5.1
  • python-sqlparse SLE Module for Package Hub 15 SP7 0.2.4-150100.6.14.1

suse advisories SUSE-SU-2026:4145-1SUSE-SU-2026:4109-1SUSE-SU-2026:23634-1SUSE-SU-2026:3978-1

  • python-sqlparse openSUSE Leap 16.0 0.5.3-160000.5.1

opensuse advisories openSUSE-SU-2026:21777-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-84305 updated cvss 6.2

sqlparse: sqlparse: Denial of Service via reindentation of tuple lists

  • Red Hat OpenStack Platform 16.2 rhosp-rhel8/openstack-ec2-api, rhosp-rhel8/openstack-tempest, rhosp-rhel8/openstack-heat-all, rhosp-rhel8/openstack-heat-api, rhosp-rhel8/openstack-keystone, rhosp-rhel8/openstack-nova-api, +68 more Red Hat OpenStack Platform 17.1 python-sqlparse, python3-sqlparse, rhosp-rhel9/openstack-horizon, rhosp-rhel9/openstack-tempest, rhosp-rhel9/openstack-aodh-api, rhosp-rhel9/openstack-heat-all, +71 more Red Hat OpenStack Platform 18.0 python-sqlparse, rhoso/openstack-horizon-rhel9, rhoso/openstack-aodh-api-rhel9, rhoso/openstack-heat-api-rhel9, rhoso/openstack-keystone-rhel9, rhoso/openstack-aodh-base-rhel9, +34 more
    under investigation
  • Red Hat OpenStack Platform 13 (Queens) python-sqlparse Red Hat OpenStack Platform 16.2 python3-sqlparse, rhosp-rhel8/openstack-aodh-api, rhosp-rhel8/openstack-aodh-base, rhosp-rhel8/openstack-aodh-notifier, rhosp-rhel8/openstack-barbican-base, rhosp-rhel8/openstack-aodh-evaluator, +3 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
2 mo ago

Exploit prediction

0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/andialbrecht/sqlparse/security/advisories/GHSA-cfqr-cjx5-5jcm referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 5.1 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 4.0 5.1 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
pypi sqlparse
<0.6.0
0.6.0

Affected products

  • andialbrecht sqlparse

Classification

Weakness
  • CWE-407 Inefficient Algorithmic Complexity

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.