Is sqlparse 0.5 vulnerable?

PyPI · 6 releases from 0.5.0 to 0.5.5 · latest sqlparse is 0.6.1 · checked 18 Nov 2026

Yes: 5 known advisories

Yes. sqlparse 0.5.5, the last 0.5 release, is affected by 5 known security advisories (3 high, 2 medium), including CVE-2026-59893, CVE-2026-54284, CVE-2026-71491. 1 more affects earlier 0.5.x releases. Upgrade to 0.6.0 or later to fix all of them.

Upgrade with:pip install 'sqlparse>=0.6.0'

Is your project on an affected sqlparse?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting sqlparse 0.5.5

  • MediumCVE-2026-84305GHSA-cfqr-cjx5-5jcm1 Sept 2026

    sqlparse: Reindentation of tuple lists causes near-cap quadratic CPU consumption

    Affected
    <0.6.0
    Fixed in
    0.6.0
  • HighCVE-2026-59893GHSA-prg7-hcfm-mfcr17 Aug 2026

    sqlparse: Inefficient Regex Handling of Dollar-Quoted SQL Literals Leads to ReDoS (Denial of Service)

    Affected
    <0.6.0
    Fixed in
    0.6.0
  • HighCVE-2026-54284GHSA-pwgv-4x5q-6m9f17 Aug 2026

    sqlparse: TokenList.__init__ materializes O(subtree) value per group, causing CPU DoS before depth/token caps trigger

    Affected
    <0.6.0
    Fixed in
    0.6.0
  • HighCVE-2026-71491GHSA-f2ff-p2ww-7p4p17 Aug 2026

    sqlparse: Quadratic O(n²) DoS in group_comments

    Affected
    <0.6.0
    Fixed in
    0.6.0
  • MediumCVE-2026-59894GHSA-3496-9g83-7v6x17 Aug 2026

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

    Affected
    <0.6.0
    Fixed in
    0.6.0

Fixed within 0.5.x, affecting earlier releases

  • MediumGHSA-27jp-wm6q-gp2513 Feb 2026

    sqlparse: formatting list of tuples leads to denial of service

    Affected
    <0.5.4
    Fixed in
    0.5.4

Every sqlparse 0.5.x release

Affected: 0.5.0 to 0.5.5. Latest sqlparse: 0.6.1.

VersionKnown advisories
sqlparse 0.5.5CVE-2026-84305, CVE-2026-59893, CVE-2026-54284, CVE-2026-71491, CVE-2026-59894
sqlparse 0.5.4CVE-2026-84305, CVE-2026-59893, CVE-2026-54284, CVE-2026-71491, CVE-2026-59894
sqlparse 0.5.3CVE-2026-84305, CVE-2026-59893, CVE-2026-54284, CVE-2026-71491, CVE-2026-59894, GHSA-27jp-wm6q-gp25
sqlparse 0.5.2CVE-2026-84305, CVE-2026-59893, CVE-2026-54284, CVE-2026-71491, CVE-2026-59894, GHSA-27jp-wm6q-gp25
sqlparse 0.5.1CVE-2026-84305, CVE-2026-59893, CVE-2026-54284, CVE-2026-71491, CVE-2026-59894, GHSA-27jp-wm6q-gp25
sqlparse 0.5.0CVE-2026-84305, CVE-2026-59893, CVE-2026-54284, CVE-2026-71491, CVE-2026-59894, GHSA-27jp-wm6q-gp25

Which of your client projects are still on sqlparse 0.5?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact sqlparse version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other sqlparse versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.