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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 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
- 31 Oct 2026, 14:10 UTC First seen by agentprime
- 31 Oct 2026, 14:10 UTC Confirmed by OSV