Algorithmic Complexity Affecting python311-sqlparse package, versions <0.4.4-150400.6.19.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.19% (8th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES155-PYTHON311SQLPARSE-19779203
  • published14 Sept 2026
  • disclosed9 Sept 2026

Introduced: 9 Sep 2026

CVE-2026-84305  (opens in a new tab)
CWE-407  (opens in a new tab)

How to fix?

Upgrade SLES:15.5 python311-sqlparse to version 0.4.4-150400.6.19.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python311-sqlparse package and not the python311-sqlparse package as distributed by SLES. See How to fix? for SLES:15.5 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1