https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 19:10:46 +0000 https://cve.radiocsirt.org/vuln/cve-2026-59894 <p><strong>Affected:</strong> andialbrecht 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> andialbrecht 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/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/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