https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 04:29:38 +0000 https://cve.radiocsirt.org/vuln/brew-athenacli-cve-2026-59894 <p><strong>Affected:</strong> Homebrew: athenacli</p> <p>### Summary</p> <p>The documented Python and PHP output modes generate source-code snippets from caller-supplied SQL. Their output filters escape quote characters without first escaping existing backslashes. Crafted SQL can therefore neutralize the generated quote escape, terminate the intended language string, and place attacker-controlled code into the generated snippet. If a downstream consumer executes or imports that generated source, the injected code runs in the consumer&#39;s environment.</p> <p>### Details</p> <p>The Python output filter places SQL in a single-quoted string and replaces each single quote with an escaped quote. The PHP output filter performs the equivalent operation for a double-quoted string. Neither transformation escapes pre-existing backslashes before escaping quotes. A backslash supplied immediately before a quote causes the generated backslash to be escaped instead of the quote, allowing the quote to close the string.</p> <p>The affected modes are exposed through `sqlparse.format(..., output_format=&#39;python&#39;)`, `sqlparse.format(..., output_format=&#39;php&#39;)`, and the corresponding `sqlformat -l` options. Formatting produces the injected source but does not itself execute it; code execution occurs when a downstream workflow treats the generated snippet as Python or PHP code.</p> <p>Relevant code locations:</p> <p>- `sqlparse/formatter.py:193` — selection of the output-language filters - `sqlparse/filters/output.py:45` — opening of the generated Python string - `sqlparse/filters/output.py:6…</p> <p><strong>Affected:</strong> Homebrew: athenacli</p> <p>### Summary</p> <p>The documented Python and PHP output modes generate source-code snippets from caller-supplied SQL. Their output filters escape quote characters without first escaping existing backslashes. Crafted SQL can therefore neutralize the generated quote escape, terminate the intended language string, and place attacker-controlled code into the generated snippet. If a downstream consumer executes or imports that generated source, the injected code runs in the consumer&#39;s environment.</p> <p>### Details</p> <p>The Python output filter places SQL in a single-quoted string and replaces each single quote with an escaped quote. The PHP output filter performs the equivalent operation for a double-quoted string. Neither transformation escapes pre-existing backslashes before escaping quotes. A backslash supplied immediately before a quote causes the generated backslash to be escaped instead of the quote, allowing the quote to close the string.</p> <p>The affected modes are exposed through `sqlparse.format(..., output_format=&#39;python&#39;)`, `sqlparse.format(..., output_format=&#39;php&#39;)`, and the corresponding `sqlformat -l` options. Formatting produces the injected source but does not itself execute it; code execution occurs when a downstream workflow treats the generated snippet as Python or PHP code.</p> <p>Relevant code locations:</p> <p>- `sqlparse/formatter.py:193` — selection of the output-language filters - `sqlparse/filters/output.py:45` — opening of the generated Python string - `sqlparse/filters/output.py:6…</p> https://cve.radiocsirt.org/vuln/brew-athenacli-cve-2026-59894 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1165 certfr-2026-avi-1165 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1165 https://cve.radiocsirt.org/vuln/cleanstart-2026-ec11110 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: apache-superset</p> <p>Multiple security vulnerabilities affect the apache-superset package. undici&#39;s retry interceptor can append the body of a ranged retry response to bytes already delivered from an earlier partial response while still presenting the original response&#39;s status and headers. See references for individual vulnerability details.</p> <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: apache-superset</p> <p>Multiple security vulnerabilities affect the apache-superset package. undici&#39;s retry interceptor can append the body of a ranged retry response to bytes already delivered from an earlier partial response while still presenting the original response&#39;s status and headers. See references for individual vulnerability details.</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-ec11110 https://cve.radiocsirt.org/vuln/euvd-2026-354743 EUVD-2026-354743 https://cve.radiocsirt.org/vuln/euvd-2026-354743 https://cve.radiocsirt.org/vuln/fkie_cve-2026-59894 <p>sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, sqlparse/filters/output.py fails to escape existing backslashes before quotes in sqlparse.format output_format=&#39;python&#39; and output_format=&#39;php&#39; and the corresponding sqlformat -l modes, allowing crafted SQL to terminate the generated string and inject Python or PHP code when a downstream consumer executes or imports the generated source. This issue is fixed in version 0.6.0.</p> <p>sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, sqlparse/filters/output.py fails to escape existing backslashes before quotes in sqlparse.format output_format=&#39;python&#39; and output_format=&#39;php&#39; and the corresponding sqlformat -l modes, allowing crafted SQL to terminate the generated string and inject Python or PHP code when a downstream consumer executes or imports the generated source. This issue is fixed in version 0.6.0.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-59894 https://cve.radiocsirt.org/vuln/ghsa-3496-9g83-7v6x <p><strong>Affected:</strong> PyPI: sqlparse</p> <p>### Summary</p> <p>The documented Python and PHP output modes generate source-code snippets from caller-supplied SQL. Their output filters escape quote characters without first escaping existing backslashes. Crafted SQL can therefore neutralize the generated quote escape, terminate the intended language string, and place attacker-controlled code into the generated snippet. If a downstream consumer executes or imports that generated source, the injected code runs in the consumer&#39;s environment.</p> <p>### Details</p> <p>The Python output filter places SQL in a single-quoted string and replaces each single quote with an escaped quote. The PHP output filter performs the equivalent operation for a double-quoted string. Neither transformation escapes pre-existing backslashes before escaping quotes. A backslash supplied immediately before a quote causes the generated backslash to be escaped instead of the quote, allowing the quote to close the string.</p> <p>The affected modes are exposed through `sqlparse.format(..., output_format=&#39;python&#39;)`, `sqlparse.format(..., output_format=&#39;php&#39;)`, and the corresponding `sqlformat -l` options. Formatting produces the injected source but does not itself execute it; code execution occurs when a downstream workflow treats the generated snippet as Python or PHP code.</p> <p>Relevant code locations:</p> <p>- `sqlparse/formatter.py:193` — selection of the output-language filters - `sqlparse/filters/output.py:45` — opening of the generated Python string - `sqlparse/filters/output.py:6…</p> <p><strong>Affected:</strong> PyPI: sqlparse</p> <p>### Summary</p> <p>The documented Python and PHP output modes generate source-code snippets from caller-supplied SQL. Their output filters escape quote characters without first escaping existing backslashes. Crafted SQL can therefore neutralize the generated quote escape, terminate the intended language string, and place attacker-controlled code into the generated snippet. If a downstream consumer executes or imports that generated source, the injected code runs in the consumer&#39;s environment.</p> <p>### Details</p> <p>The Python output filter places SQL in a single-quoted string and replaces each single quote with an escaped quote. The PHP output filter performs the equivalent operation for a double-quoted string. Neither transformation escapes pre-existing backslashes before escaping quotes. A backslash supplied immediately before a quote causes the generated backslash to be escaped instead of the quote, allowing the quote to close the string.</p> <p>The affected modes are exposed through `sqlparse.format(..., output_format=&#39;python&#39;)`, `sqlparse.format(..., output_format=&#39;php&#39;)`, and the corresponding `sqlformat -l` options. Formatting produces the injected source but does not itself execute it; code execution occurs when a downstream workflow treats the generated snippet as Python or PHP code.</p> <p>Relevant code locations:</p> <p>- `sqlparse/formatter.py:193` — selection of the output-language filters - `sqlparse/filters/output.py:45` — opening of the generated Python string - `sqlparse/filters/output.py:6…</p> https://cve.radiocsirt.org/vuln/ghsa-3496-9g83-7v6x https://cve.radiocsirt.org/vuln/oesa-2026-4218 <p><strong>Affected:</strong> openEuler:24.03-LTS-SP3: python-sqlparse</p> <p>A non-validating SQL parser. Security Fix(es):</p> <p>sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, TokenList construction and string conversion in sqlparse/sql.py repeatedly flatten nested token subtrees constructed by group_parenthesis and group_case, causing quadratic CPU consumption through sqlparse.parse(), sqlparse.format(), and sqlparse.split() before depth and token limits terminate processing. This issue is fixed in version 0.6.0.(CVE-2026-54284)</p> <p>sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, sqlparse/filters/output.py fails to escape existing backslashes before quotes in sqlparse.format output_format=&amp;apos;python&amp;apos; and output_format=&amp;apos;php&amp;apos; and the corresponding sqlformat -l modes, allowing crafted SQL to terminate the generated string and inject Python or PHP code when a downstream consumer executes or imports the generated source. This issue is fixed in version 0.6.0.(CVE-2026-59894)</p> <p>sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, group_comments in sqlparse/engine/grouping.py repeatedly rescans comment-only statements before the MAX_GROUPING_TOKENS guard, causing quadratic CPU consumption through sqlparse.parse() and sqlparse.format(sql, strip_comments=True). This issue is fixed in version 0.6.0.(CVE-2026-71491)</p> <p><strong>Affected:</strong> openEuler:24.03-LTS-SP3: python-sqlparse</p> <p>A non-validating SQL parser. Security Fix(es):</p> <p>sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, TokenList construction and string conversion in sqlparse/sql.py repeatedly flatten nested token subtrees constructed by group_parenthesis and group_case, causing quadratic CPU consumption through sqlparse.parse(), sqlparse.format(), and sqlparse.split() before depth and token limits terminate processing. This issue is fixed in version 0.6.0.(CVE-2026-54284)</p> <p>sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, sqlparse/filters/output.py fails to escape existing backslashes before quotes in sqlparse.format output_format=&amp;apos;python&amp;apos; and output_format=&amp;apos;php&amp;apos; and the corresponding sqlformat -l modes, allowing crafted SQL to terminate the generated string and inject Python or PHP code when a downstream consumer executes or imports the generated source. This issue is fixed in version 0.6.0.(CVE-2026-59894)</p> <p>sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, group_comments in sqlparse/engine/grouping.py repeatedly rescans comment-only statements before the MAX_GROUPING_TOKENS guard, causing quadratic CPU consumption through sqlparse.parse() and sqlparse.format(sql, strip_comments=True). This issue is fixed in version 0.6.0.(CVE-2026-71491)</p> https://cve.radiocsirt.org/vuln/oesa-2026-4218 https://cve.radiocsirt.org/vuln/opensuse-su-2026:11557-1 <p>python313-sqlparse-0.6.0-1.1 on GA media</p> <p>python313-sqlparse-0.6.0-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2026:11557-1 https://cve.radiocsirt.org/vuln/pysec-2026-3696 <p><strong>Affected:</strong> PyPI: sqlparse</p> <p>### Summary</p> <p>The documented Python and PHP output modes generate source-code snippets from caller-supplied SQL. Their output filters escape quote characters without first escaping existing backslashes. Crafted SQL can therefore neutralize the generated quote escape, terminate the intended language string, and place attacker-controlled code into the generated snippet. If a downstream consumer executes or imports that generated source, the injected code runs in the consumer&#39;s environment.</p> <p>### Details</p> <p>The Python output filter places SQL in a single-quoted string and replaces each single quote with an escaped quote. The PHP output filter performs the equivalent operation for a double-quoted string. Neither transformation escapes pre-existing backslashes before escaping quotes. A backslash supplied immediately before a quote causes the generated backslash to be escaped instead of the quote, allowing the quote to close the string.</p> <p>The affected modes are exposed through `sqlparse.format(..., output_format=&#39;python&#39;)`, `sqlparse.format(..., output_format=&#39;php&#39;)`, and the corresponding `sqlformat -l` options. Formatting produces the injected source but does not itself execute it; code execution occurs when a downstream workflow treats the generated snippet as Python or PHP code.</p> <p>Relevant code locations:</p> <p>- `sqlparse/formatter.py:193` — selection of the output-language filters - `sqlparse/filters/output.py:45` — opening of the generated Python string - `sqlparse/filters/output.py:6…</p> <p><strong>Affected:</strong> PyPI: sqlparse</p> <p>### Summary</p> <p>The documented Python and PHP output modes generate source-code snippets from caller-supplied SQL. Their output filters escape quote characters without first escaping existing backslashes. Crafted SQL can therefore neutralize the generated quote escape, terminate the intended language string, and place attacker-controlled code into the generated snippet. If a downstream consumer executes or imports that generated source, the injected code runs in the consumer&#39;s environment.</p> <p>### Details</p> <p>The Python output filter places SQL in a single-quoted string and replaces each single quote with an escaped quote. The PHP output filter performs the equivalent operation for a double-quoted string. Neither transformation escapes pre-existing backslashes before escaping quotes. A backslash supplied immediately before a quote causes the generated backslash to be escaped instead of the quote, allowing the quote to close the string.</p> <p>The affected modes are exposed through `sqlparse.format(..., output_format=&#39;python&#39;)`, `sqlparse.format(..., output_format=&#39;php&#39;)`, and the corresponding `sqlformat -l` options. Formatting produces the injected source but does not itself execute it; code execution occurs when a downstream workflow treats the generated snippet as Python or PHP code.</p> <p>Relevant code locations:</p> <p>- `sqlparse/formatter.py:193` — selection of the output-language filters - `sqlparse/filters/output.py:45` — opening of the generated Python string - `sqlparse/filters/output.py:6…</p> https://cve.radiocsirt.org/vuln/pysec-2026-3696 https://cve.radiocsirt.org/vuln/suse-su-2026:23561-1 <p>Security update for python-sqlparse</p> <p>Security update for python-sqlparse</p> https://cve.radiocsirt.org/vuln/suse-su-2026:23561-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-59894 <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: sqlparse, Ubuntu:Pro:18.04:LTS: sqlparse, Ubuntu:Pro:20.04:LTS: sqlparse, Ubuntu:22.04:LTS: sqlparse, Ubuntu:24.04:LTS: sqlparse, Ubuntu:26.04:LTS: sqlparse</p> <p>sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, sqlparse/filters/output.py fails to escape existing backslashes before quotes in sqlparse.format output_format=&#39;python&#39; and output_format=&#39;php&#39; and the corresponding sqlformat -l modes, allowing crafted SQL to terminate the generated string and inject Python or PHP code when a downstream consumer executes or imports the generated source. This issue is fixed in version 0.6.0.</p> <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: sqlparse, Ubuntu:Pro:18.04:LTS: sqlparse, Ubuntu:Pro:20.04:LTS: sqlparse, Ubuntu:22.04:LTS: sqlparse, Ubuntu:24.04:LTS: sqlparse, Ubuntu:26.04:LTS: sqlparse</p> <p>sqlparse is a non-validating SQL parser module for Python. Prior to 0.6.0, sqlparse/filters/output.py fails to escape existing backslashes before quotes in sqlparse.format output_format=&#39;python&#39; and output_format=&#39;php&#39; and the corresponding sqlformat -l modes, allowing crafted SQL to terminate the generated string and inject Python or PHP code when a downstream consumer executes or imports the generated source. This issue is fixed in version 0.6.0.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-59894