Advisory record · GHSA-3496-9g83-7v6x

sqlparse: Generated Python and PHP snippets allow SQL string breakout through unescaped backslashes

CVSS 6.2 MediumEPSS 0.0013 · 2nd percentile

Published by the GitHub Advisory Database at 17 Aug 2026, 17:20 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
sqlparsePyPI<0.6.00.6.0
Identifiers
GHSA-3496-9g83-7v6x · CVE-2026-59894 · PYSEC-2026-3696
Weakness (CWE)
CWE-94
Published
17 Aug 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

sqlparse versions before 0.6.0 are vulnerable when the Python or PHP output formats are used. Their quote escaping does not first escape existing backslashes, so crafted SQL can break out of the generated string literal. An attacker who controls the SQL must also have a downstream consumer execute or import the generated snippet, which then runs the injected code with that process's permissions. Upgrade to sqlparse 0.6.0 or later. Avoid the Python and PHP output modes for untrusted SQL until then.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.2 Medium 4.0 CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0013, the 2nd percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:10 UTC First seen by agentprime
  2. 31 Oct 2026, 14:10 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.