https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 18:39:01 +0000 https://vulnerability.circl.lu/vuln/cve-2026-59893 <p><strong>Affected:</strong> andialbrecht sqlparse</p> <p>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.</p> <p><strong>Affected:</strong> andialbrecht sqlparse</p> <p>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.</p> https://vulnerability.circl.lu/vuln/cve-2026-59893 https://vulnerability.circl.lu/vuln/ghsa-prg7-hcfm-mfcr <p><strong>Affected:</strong> PyPI: sqlparse</p> <p>### Summary</p> <p>sqlparse contains a Regular Expression Denial of Service (ReDoS) vulnerability in its dollar-quoted SQL literal lexer. The regex pattern at `sqlparse/keywords.py:33` uses a backreference (`\1`) to match closing dollar-quote delimiters, causing O(n²) CPU complexity when processing inputs containing many unique, unmatched dollar-quote opening sequences. An attacker who can supply arbitrary SQL text to any application using sqlparse can trigger sustained CPU exhaustion, resulting in a denial of service. No authentication or special privileges are required.</p> <p>**Scope note:** the same regex shape — a lazy dot-all quantifier terminated by a delimiter, applied at every input position by the lexer loop — is also present in the two multiline-comment patterns. Those are covered by this advisory and by the same fix; see &#34;Additional affected pattern: multiline comments&#34; below.</p> <p>### Details</p> <p>The vulnerable regex is defined in `sqlparse/keywords.py` as part of `SQL_REGEX`:</p> <p>```python # sqlparse/keywords.py:33 (r&#39;((?&lt;![\w\&#34;\$])\$(?:[_A-ZÀ-Ü]\w*)?\$)[\s\S]*?\1&#39;, tokens.Literal), ```</p> <p>This pattern first captures a dollar-quote delimiter (e.g., `$tag$`) into group 1, then attempts to match any characters (`[\s\S]*?`) up to the same delimiter again via backreference `\1`. When no matching closing delimiter exists, the regex engine exhausts the remaining input before concluding there is no match. For a sequence of N unique unmatched openers, each opener triggers a full scan of the r…</p> <p><strong>Affected:</strong> PyPI: sqlparse</p> <p>### Summary</p> <p>sqlparse contains a Regular Expression Denial of Service (ReDoS) vulnerability in its dollar-quoted SQL literal lexer. The regex pattern at `sqlparse/keywords.py:33` uses a backreference (`\1`) to match closing dollar-quote delimiters, causing O(n²) CPU complexity when processing inputs containing many unique, unmatched dollar-quote opening sequences. An attacker who can supply arbitrary SQL text to any application using sqlparse can trigger sustained CPU exhaustion, resulting in a denial of service. No authentication or special privileges are required.</p> <p>**Scope note:** the same regex shape — a lazy dot-all quantifier terminated by a delimiter, applied at every input position by the lexer loop — is also present in the two multiline-comment patterns. Those are covered by this advisory and by the same fix; see &#34;Additional affected pattern: multiline comments&#34; below.</p> <p>### Details</p> <p>The vulnerable regex is defined in `sqlparse/keywords.py` as part of `SQL_REGEX`:</p> <p>```python # sqlparse/keywords.py:33 (r&#39;((?&lt;![\w\&#34;\$])\$(?:[_A-ZÀ-Ü]\w*)?\$)[\s\S]*?\1&#39;, tokens.Literal), ```</p> <p>This pattern first captures a dollar-quote delimiter (e.g., `$tag$`) into group 1, then attempts to match any characters (`[\s\S]*?`) up to the same delimiter again via backreference `\1`. When no matching closing delimiter exists, the regex engine exhausts the remaining input before concluding there is no match. For a sequence of N unique unmatched openers, each opener triggers a full scan of the r…</p> https://vulnerability.circl.lu/vuln/ghsa-prg7-hcfm-mfcr https://vulnerability.circl.lu/vuln/pysec-2026-3698 <p><strong>Affected:</strong> PyPI: sqlparse</p> <p>### Summary</p> <p>sqlparse contains a Regular Expression Denial of Service (ReDoS) vulnerability in its dollar-quoted SQL literal lexer. The regex pattern at `sqlparse/keywords.py:33` uses a backreference (`\1`) to match closing dollar-quote delimiters, causing O(n²) CPU complexity when processing inputs containing many unique, unmatched dollar-quote opening sequences. An attacker who can supply arbitrary SQL text to any application using sqlparse can trigger sustained CPU exhaustion, resulting in a denial of service. No authentication or special privileges are required.</p> <p>**Scope note:** the same regex shape — a lazy dot-all quantifier terminated by a delimiter, applied at every input position by the lexer loop — is also present in the two multiline-comment patterns. Those are covered by this advisory and by the same fix; see &#34;Additional affected pattern: multiline comments&#34; below.</p> <p>### Details</p> <p>The vulnerable regex is defined in `sqlparse/keywords.py` as part of `SQL_REGEX`:</p> <p>```python # sqlparse/keywords.py:33 (r&#39;((?&lt;![\w\&#34;\$])\$(?:[_A-ZÀ-Ü]\w*)?\$)[\s\S]*?\1&#39;, tokens.Literal), ```</p> <p>This pattern first captures a dollar-quote delimiter (e.g., `$tag$`) into group 1, then attempts to match any characters (`[\s\S]*?`) up to the same delimiter again via backreference `\1`. When no matching closing delimiter exists, the regex engine exhausts the remaining input before concluding there is no match. For a sequence of N unique unmatched openers, each opener triggers a full scan of the r…</p> <p><strong>Affected:</strong> PyPI: sqlparse</p> <p>### Summary</p> <p>sqlparse contains a Regular Expression Denial of Service (ReDoS) vulnerability in its dollar-quoted SQL literal lexer. The regex pattern at `sqlparse/keywords.py:33` uses a backreference (`\1`) to match closing dollar-quote delimiters, causing O(n²) CPU complexity when processing inputs containing many unique, unmatched dollar-quote opening sequences. An attacker who can supply arbitrary SQL text to any application using sqlparse can trigger sustained CPU exhaustion, resulting in a denial of service. No authentication or special privileges are required.</p> <p>**Scope note:** the same regex shape — a lazy dot-all quantifier terminated by a delimiter, applied at every input position by the lexer loop — is also present in the two multiline-comment patterns. Those are covered by this advisory and by the same fix; see &#34;Additional affected pattern: multiline comments&#34; below.</p> <p>### Details</p> <p>The vulnerable regex is defined in `sqlparse/keywords.py` as part of `SQL_REGEX`:</p> <p>```python # sqlparse/keywords.py:33 (r&#39;((?&lt;![\w\&#34;\$])\$(?:[_A-ZÀ-Ü]\w*)?\$)[\s\S]*?\1&#39;, tokens.Literal), ```</p> <p>This pattern first captures a dollar-quote delimiter (e.g., `$tag$`) into group 1, then attempts to match any characters (`[\s\S]*?`) up to the same delimiter again via backreference `\1`. When no matching closing delimiter exists, the regex engine exhausts the remaining input before concluding there is no match. For a sequence of N unique unmatched openers, each opener triggers a full scan of the r…</p> https://vulnerability.circl.lu/vuln/pysec-2026-3698